Device-aware communication requests

ABSTRACT

This disclosure describes, in part, techniques for enabling merchant devices to interoperate with one another in a more robust manner, such that overall operation and efficiency within a merchant establishment is improved. For instance, the techniques described herein may enable the intelligent routing of requests between devices within the merchant establishment based on real-time locations of the devices, which devices are associated with which orders, and the like.

TECHNICAL FIELD

More and more merchants are utilizing electronic devices and associatedcomputing applications to aid in the operation of their respectivebusinesses. For instance, retail establishments often use point-of-sale(POS) devices for processing payments, updating and accessing inventorylevels, and/or the like. Restaurant establishments may also equip theirservers and other staff with mobile POS devices for ordering items onbehalf of customers, scheduling preparation of the items, and so forth.As use of these devices increases, so too do merchant desires for moreintelligent applications executing on the devices.

BRIEF DESCRIPTION OF THE DRAWINGS

Features of the present disclosure, its nature and various advantages,will be more apparent upon consideration of the following detaileddescription, taken in conjunction with the accompanying drawings.

FIG. 1 illustrates an example environment in which a first user in anestablishment operates a back-of-house (BOH) device to request a serverthat placed an order whose details are presented on the BOH device. Inresponse, the BOH device may determine a front-of-house (FOH) devicethat placed the order, establish a communication session of with the FOHdevice, and send a request for the server to the FOH device.

FIG. 2 illustrates example components of the BOH and/or FOH devicesdescribed herein for performing the technique described herein.

FIG. 3 illustrates a flow diagram of an example process for establishinga communication session between a BOH device and an FOH device forsending, to the FOH device, a request regarding an order placed by theFOH device.

FIG. 4 illustrates a flow diagram of another example process forestablishing a communication session between a BOH device and an FOHdevice for sending, to the FOH device, an indication that an itemassociated with an order placed by the FOH device has been prepared.

FIG. 5 illustrates a flow diagram of another example process forestablishing a communication session between a BOH device and an FOHdevice for sending, to the FOH device, an indication that a user hasbegun preparing an item associated with an order placed by the FOHdevice.

FIG. 6 illustrates a flow diagram of another example process forreceiving a request to activate an appliance to handle a currentcapacity of orders.

FIG. 7 illustrates an example user interface (UI) that a BOH device maydisplay for presenting current orders that are to be prepared. FIG. 7also illustrates that an operator of the BOH device selects to viewdetails regarding a first displayed order.

FIG. 8 illustrates another example UI that a BOH device may display inresponse to the selection shown in FIG. 7 . Here, the selected order isexpanding to present additional details regarding the order and optionsregarding the order.

FIG. 9 illustrates another example UI that a BOH device may displayafter the UI shown in FIG. 8 . Here, UI provides options for theoperator of the BOH device, including an option to request a server thatplaced the order.

FIG. 10 illustrates another example UI that a FOH device may display inresponse to the selection by the operator of the BOH device shown inFIG. 9 .

FIG. 11 illustrates another example UI that a BOH device associated withan expeditor station may display. Here, an operator of the BOH deviceselects an item associated with a particular order.

FIG. 12 illustrates another example UI that a BOH device associated withthe expeditor station may display in response to the selection of FIG.11 . As illustrated, the BOH device may present several options to theoperator including an option to request to make the item now, which theoperator selects.

FIG. 13 illustrates another example UI that a BOH device associated witha preparation station may display prior to the selection at theexpeditor station shown in FIG. 12 . As illustrated, this UI mayprioritize preparation of different orders in the establishment.

FIG. 14 illustrates another example UI that the BOH device of FIG. 13may display after the selection at the expeditor station shown in FIG.12 . As illustrated, this UI includes an indication that the expeditorhas requested that the preparation station begin preparing a certainitem.

FIG. 15 illustrates another example UI that the BOH device of FIG. 13may display after the operator of the device selects, via the UI of FIG.14 , the option to start the order requested by the expeditor. Asillustrated, the displayed orders have been reprioritized in response tothis selection.

FIG. 16 illustrates another example UI that a BOH device may display.Here, the UI presents various kitchen-performance metrics.

FIG. 17 illustrates another example UI that the BOH device may display.Here, the UI presents certain suggestions for operation of theestablishment, such as a suggestion to activate an additional fryerstation. The UI also includes an icon for automatically activating thesuggested fryer station.

FIG. 18 illustrates another example UI that the BOH device may displayafter the operator of the device selects the icon shown in FIG. 17 .

FIG. 19 illustrates another example UI that the BOH device may displayafter the UI shown in FIG. 18 . As illustrated, the UI indicates thatorders previously assigned to other fryer stations have now been movedto the recently activated fryer station.

FIG. 20 illustrates another example UI that the BOH device may display.Here, the UI indicates certain orders and an icon for indicating that aparticular order has been started.

FIG. 21 illustrates another example UI that an FOH device may presentfor informing an operator of the FOH device of the current status oforders that the operator has placed to the BOH. For instance, this UIindicates that one order is ready for delivery, another order is nearlycomplete, and a third order is half complete.

FIG. 22 illustrates another example UI that an FOH device may display toprovide information to the operator of the FOH device.

FIG. 23 illustrates the example environment of FIG. 1 . Here, a firstFOH device is near a first location in the establishment associated witha first order and, thus, presents a request or suggestion that a serverof the first FOH device perform a certain action associated with thefirst order. Additionally, a second FOH device is near a second locationthat is associated with a second order and, thus, presents a request orsuggestion that a server of the second FOH device perform a second,different action associated with the second order.

FIG. 24 illustrates a flow diagram of an example process for determiningthat a particular FOH device is within a threshold proximity of a firstlocation and, in response, sending a UI to the FOH device requesting orsuggesting a particular action associated with the first location.

FIG. 25 illustrates a flow diagram of another example process fordetermining that the FOH device is within a threshold proximity of asecond location and, in response, sending a second UI to the FOH devicerequesting or suggesting a particular action associated with the secondlocation.

FIG. 26 illustrates a flow diagram of another example process fordetermining that the FOH device is within a threshold proximity of athird location and, in response, sending a third UI to the FOH devicerequesting or suggesting a particular action associated with the thirdlocation.

FIG. 27 illustrates a flow diagram of another example process forenabling an operator of a FOH device to add items to an order.

FIG. 28 illustrates a flow diagram of another example process fordetermining an item to suggest for addition to a first order andpresenting the suggestion on an FOH device in response to the FOH beingwithin a threshold proximity of a first location associated with thefirst order.

FIG. 29 illustrates a flow diagram of another example process fordetermining the identity of an operator of an FOH device, determiningwhether the identity is associated with prior behavior and, if so,presenting a UI that includes a sequence of actions that have beencustomized to the operator based on the prior behavior.

FIG. 30 illustrates a flow diagram of another example process fordetermining if an FOH device is physically coupled to, or within athreshold proximity of, another device and, if so, presenting a UIindicating a sequence of actions to perform.

FIG. 31 illustrates an example UI that an FOH device may present inresponse to being located with a threshold proximity of a particularlocation in an establishment. As illustrated, this UI suggests that anoperator of the FOH device print a bill for customer(s) located near theparticular location.

FIG. 32 illustrates another example UI that an FOH device may present inresponse to being located with a threshold proximity of a particularlocation in an establishment. As illustrated, this UI suggests that anoperator of the FOH device request to fire a course ordered bycustomer(s) located near the particular location.

FIG. 33 illustrates another example UI that an FOH device may present inresponse to being located with a threshold proximity of a particularlocation in an establishment. As illustrated, this UI suggests that anoperator of the FOH device request to open a table or order forassociated with the particular location, given that the table is notcurrently associated with an open order.

FIG. 34 illustrates another example UI that an FOH device may present.As illustrated, this UI illustrates items available to be ordered and alayout of the establishment. Using this UI, an operator of the FOHdevice may add an item to an order associated with a particular table orseating area by dragging an icon associated with the icon to an iconassociated with the table or seating area.

FIG. 35 illustrates another example UI that the FOH of FIG. 34 maypresent as the operator drags the icon associated with the item towardsan icon associated with a table or seating area.

FIG. 36 illustrates another example UI that the FOH of FIG. 34 maypresent just before the operator “drops” the icon associated with theitem on an icon associated with a table or seating area.

FIG. 37 illustrates another example UI that the FOH of FIG. 34 maypresent after the UI of FIG. 36 . Here, the item (“Chips and Guac”) hasbeen added to an order associated with table 2. In addition, the UIpresents a timer that is set for a predefined amount of time, afterexpiration of which the FOH device may send the order to a BOH device inthe establishment for preparation of the order.

FIG. 38 illustrates another example UI that the FOH of FIG. 34 maypresent, showing that an operator of the FOH device has added anotheritem to table 2.

FIG. 39 illustrates another example UI that the FOH device of FIG. 34may present after the operator has added the second item. Here, the item(“Bud Bucket”) has been added to the order and the timer has been re-setin response to the second item being added to the order.

FIG. 40 illustrates another example UI that the FOH device of FIG. 34may present after the operator of the FOH device has selected the iconassociated with table 2. Here, the UI includes an operation to send tothe order to the BOH device for preparation of the order prior toexpiration of the timer.

FIG. 41 illustrates another example UI that an FOH device may present.Here, the UI includes suggested items or actions, which may be presentedin response to the FOH device being within a threshold proximity of aparticular location in the establishment.

FIG. 42 illustrates another example UI that an FOH device may present.Here, the UI includes different suggested items or actions, which may bepresented in response to the FOH device being within a thresholdproximity of a particular location in the establishment.

FIG. 43 illustrates another example UI that an FOH device may present.Here, the UI includes different actions that the operator may perform.

FIG. 44 illustrates another example UI that an FOH device of FIG. 41 maypresent. Here, the operator of the FOH device requests to perform thesuggested actions, which may be customized based on prior behavior ofthe current operator of the FOH device.

FIG. 45 illustrates another example UI that the FOH device of FIG. 44may present after the selection shown in FIG. 44 . Here, the UIillustrates details regarding tips received by the operator of the FOHdevice and an icon for viewing details regarding the shift of theoperator.

FIG. 46 illustrates another example UI that the FOH device after theselection shown in FIG. 45 . Here, the UI illustrates shift details andincludes an icon for allowing the operator to run a shift report.

FIG. 47 illustrates another example UI that the FOH device after theselection shown in FIG. 46 . Here, the UI indicates that the FOH deviceis running a shift report for the operator.

FIG. 48 illustrates another example UI that the FOH device after therunning of the shift report shown in FIG. 47 .

FIG. 49 illustrates an example UI that an FOH device may present priorto being coupled to or within a threshold proximity of another device.

FIG. 50 illustrates another example UI that the FOH device of FIG. 49may present after being physically coupled to another device, such as acradle. As illustrated, the FOH device may begin running a shift reportautomatically in response to being physical coupled to the cradle.

FIG. 51 continues the illustration of FIG. 50 and shows that tips arebeing transferred to an account associated with an operator of the FOHdevice.

FIG. 52 concludes the illustration of the FIG. 50 and shows that theoperator has been logged out of the FOH device.

FIG. 53 illustrates another example UI that an FOH device may perform inresponse to being coupled to or within a threshold proximity of anotherdevice. In this example, the FOH device detects that it is within athreshold proximity of a tableside device (e.g., another FOH device)and, thus, presents a suggestion to open an order.

FIG. 54 illustrates an example UI that the FOH device of FIG. 53 maypresent in response to opening the order.

FIG. 55 and subsequent UIs illustrate different gestures that may beassociated with different actions. Here, the UI illustrates differentoptions associated with a particular item (“the burger”), with anoperator of the FOH device having selected one particular option(“lettuce”).

FIG. 56 continues the illustration of the UI of FIG. 55 and illustratesthe operator of the FOH device swiping the selected icon to the right.

FIG. 57 continues the illustration of the UI of FIG. 56 and shows thatthe selected option (“lettuce”) has been added to the item in responseto operator swiping the icon to the right.

FIG. 58 continues the illustration of the UI of FIG. 57 and shows theoperator swiping the icon associated with the selected option to theleft. In response, the UI indicates that the selected option (“lettuce”)has been removed from the item.

FIG. 59 illustrates the operator selecting another example option(“onions”).

FIG. 60 continues the illustration of the UI of FIG. 59 and illustratesthe operator swiping the icon associated with the option upwards.

FIG. 61 continues the illustration of the UI of FIG. 60 and illustratesthat an extra amount of the selection option (“onions”) has been addedto the order in response to the upward swipe. In addition, this UIillustrates that the operator now swipes the icon downwards and, inresponse, indicates that the option will be provided on the side.

FIG. 62 continues the illustration of the UI of FIG. 61 and illustratesthat the extra amount of the selection option has been changed to a sideof the selected option in response to the downwards swiping of the icon.

FIG. 63 and subsequent UIs illustrate other example UIs and gestures forperforming different actions. Here, an operator of the FOH device hasselected one example option (“Bacon”).

FIG. 64 illustrates an example UI that the FOH device may present inresponse to the selection shown in FIG. 63 . Here, different modifiersassociated with the option are presented.

FIG. 65 continues the illustration of the UI of FIG. 64 and illustratesthe operator dragging the option (“Bacon”) to one of the presentedmodifiers (“Extra”). In response, the icon associated with the selectedmodifiers has enlarged.

FIG. 66 continues the illustration of the UI of FIG. 65 and illustratesthat the icon corresponding to the selected modifier now displays anindication of the option, in addition to the modifier itself (“ExtraBacon”).

FIG. 67 illustrates an example UI that the FOH may present after the UIof FIG. 66 . Here, the modifiers are removed from the display, but theinitial UI of FIG. 63 has been altered to indicate the selection madeabove.

FIG. 68 and subsequent UIs illustrate still other example UIs andgestures for performing different actions. Here, an operator of the FOHdevice has selected one example option (“Lettuce”).

FIG. 69 continues the illustration of the UI of FIG. 68 and illustratesthat a number of modifiers have been presented adjacent the selectedicon (“Lettuce”). In addition, this UI illustrates that the operatorswipes upwards from the selected icon.

FIG. 70 continues the illustration of the UI of FIG. 69 and illustratesthat the locations of the modifiers have changed in response to theupward swipe of the operation in FIG. 69 . For example, a modifierentitled “extra” is now adjacent the “lettuce” icon rather than “add”,as was previously adjacent this icon.

FIG. 71 continues the illustration of the UI of FIG. 70 and shows anexample UI after a user has swiped downwards such that a modifier of“no” is adjacent the icon for “lettuce”.

FIG. 72 illustrates an example UI that the FOH device may present afterthe selection of FIG. 71 . As illustrated, the UI indicates that theitem is to have “no lettuce”. In addition, the operator has selected anicon corresponding to another option (“Fried Onions”).

FIG. 73 illustrates an example UI that the device may present after theselection of FIG. 72 . Again, the modifiers may appear adjacent the iconfor the selected option and the operator may select one of the modifiersby swiping upwards and/or downwards until the desired modifier isadjacent to the selected option.

FIG. 74 illustrates the example environment of FIG. 1 . Here, a merchantoperates a merchant device to capture data (e.g., image data) of theestablishment. The merchant device then sends the data to a remoteservice, which analyzes the data to identify flat surfaces in theenvironment and to send, back to the merchant device, a UI forindicating which flat surfaces correspond to seating areas and which donot. After receiving the respective indications from the merchant, theservice may generate and present on the merchant device a layout ofavailable seating areas in the establishment.

FIG. 75 illustrates a flow diagram of an example process for generatinga layout of available seating areas in an establishment.

FIG. 76 illustrates a flow diagram of another example process fordetermining a suggested layout of available seating areas in anestablishment.

FIG. 77 illustrates a flow diagram of another example process forgenerating a layout of example seating areas in an establishment.

FIG. 78 illustrates an example UI that a merchant device may presentafter scanning an establishment of the merchant. As illustrated, the UIindicates which surfaces in the establishment have been identified asflat surfaces and enables the merchant to select which of the identifiedflat surfaces are in fact available seating areas.

FIG. 79 illustrates an example UI after the merchant has indicated, viathe UI from FIG. 78 , that all three tables are available seating areas.This UI also provides an option to the merchant to continue scanning theestablishment or to generate a layout of available seating areas.

FIG. 80 illustrates an example UI that the merchant device may presentafter the merchant requests to view a generated layout via the UI ofFIG. 79 . As illustrated, this UI presents a generated layout ofavailable seating areas in the establishment of the merchant.

FIG. 81 is an example network environment in which the describedtechniques may be implemented.

FIG. 82 are example hardware and/or software modules that may implementthe described techniques.

In the figures, the left-most digit(s) of a reference number identifiesthe figure in which the reference number first appears. The use of thesame reference numbers in different figures indicates similar oridentical items or features. The drawings are not to scale.

DETAILED DESCRIPTION

As described above, more and more merchants are utilizing electronicdevices and associated computing applications to aid in the operation oftheir respective businesses. For instance, retail establishments oftenuse point-of-sale (POS) devices for processing payments, updating andaccessing inventory levels, and/or the like. Restaurant establishmentsmay also equip their servers and other staff with mobile POS devices forordering items on behalf of customers, scheduling preparation of theitems, and so forth.

Despite the use and advancement of these devices, these devices oftenoperate in a standalone manner. For example, a server within arestaurant may utilize a mobile front-of-house (FOH) device for takingorders from customers and submitting them for preparation to aback-of-house (BOH) device, generally not viewable by the customers. Acook, chef, expeditor, or other user of the BOH device, meanwhile, mayuse the BOH device to view current orders to prepare the orders. Instill other instances, a host or hostess may utilize another FOH deviceto maintain a waiting list for customers awaiting seating in theestablishment. In general, however, these devices provide functionalityfor their given tasks, and often do not interact with the other devicesto improve the general operation of the establishment.

This disclosure describes, in part, techniques for enabling these typesof merchant devices to interoperate with one another in a more robustmanner, such that overall operation and efficiency within a merchantestablishment is improved at least through intelligent and dynamicallychanging device-to-device and device-to-network connections. Forinstance, the techniques described herein may enable the intelligentrouting of requests between devices within the merchant establishmentbased on real-time locations of the devices, which devices areassociated with which orders, proximity of the devices to the customersor customer locations (e.g., seating areas), and the like. Further, suchrouting may be optimized based on contextual information, such as timeof the day, network usage, device usage, and other such metrics. Toprovide an example, a first server within a restaurant may operate afirst FOH for inputting orders to a BOH device. A second server,meanwhile, may operate a second FOH for also inputting orders to the BOHdevice. The BOH device may receive the orders from each of these FOHdevices (and, potentially, many others) and may present, on a display ofthe BOH device, details regarding each order that need be prepared forthe respective customers. For example, the BOH device may display aprioritized list of orders such that one or more BOH employees at therestaurant may view the display and determine how and in what order toprepare the orders.

If, however, a cook, chef, food runner, expeditor, or other BOH employeehas a question regarding an order, that employee may utilize the BOHdevice to request clarification. For example, the employee may select anorder, or an individual item from an order, from the BOH device and mayinput a request to speak with a server that is responsible for placingthe order. In response to receiving this request, the BOH device maydetermine which of the multiple FOH devices placed the order with theBOH device. In response to identifying the responsible FOH devices, theBOH device may establish a dedicated communication session with the FOHdevice and may send the request or query to the FOH device. For example,the BOH device may establish a short-range wireless connection (e.g.,Bluetooth, Zigbee, etc.) with the FOH device, may establish a connectionover Wi-Fi, may establish a connection over the Internet, or the likefor routing the request to the FOH device. In some embodiments, the typeof connection is based at least on device characteristics, the nature orsize of data packet being sent over the channel, or the like.

The FOH device may, in turn, receive the request from the BOH device andmay output data indicative of the request, such as displaying therequest on a display of the FOH device. For example, the FOH device maypresent an indication that a particular BOH device associated with aparticular location in the restaurant has requested clarification on aparticular order placed by the FOH device. The server may, in turn, goto the specified location to clarify the order, as requested. In anotherexample, the communication session may enable a back-and-forth dialoguebetween the operator of the BOH device and the server operating the FOHdevice. For example, the communication session may enable a video chat,a voice chat, an instant-messaging chat, or any other type ofinteractive dialogue involving audio, visual, or haptic inputs from oneor both parties.

Thus, the techniques described herein may create real-time or nearreal-time communication sessions between devices, with the initiatingdevice automatically identifying the device to connect to. As usedherein, real-time communication sessions may represent sessions createdsubstantially contemporaneously with an event (e.g., within 1 second,100 milliseconds, etc. of a communication request), while near-real-timecommunication sessions may represent sessions created within a greaterthreshold amount of time after an event (e.g., within a few seconds, oneminute, etc. of a communication request). Furthermore, the techniquesdescribed herein allow switching between devices thereby creating uniquesessions one after the other, sometimes even allowing multiple devicesto communicate with each other for a predetermined time period or for aspecific order. For example, the BOH device may automatically identifythe FOH device to establish the communication session with based on theFOH device having previously input the order in question. In anotherexample, the BOH device may automatically ping the FOH device closest tothe table from which the order in question was placed. The generatedcommunication session may stay open for a predetermined amount of time(e.g., one minute, five minutes, etc.), until completion of a request,and/or the like. The automatic establishment of a communication sessionin real-time provides at least some of the technological advancementsdiscussed herein. For instance, the generating of these real-timecommunication sessions creates groups of inter-operable devices ratherthan individual devices that generally function singularly. Further, byautomatically identifying the appropriate FOH device to connect to, thetechniques eliminate the need to analyze details regarding individualorders to determine the server or device that provided the particularorder. Instead, an operator of the BOH device may issue the request andthe BOH device may automatically create the appropriate communicationchannel. These efficiencies may be particularly important inestablishments, such as restaurants that handle large volumes of ordersand move at an extremely quick pace. Further, using the techniquesdescribed herein, FOH devices may identify and initiate connections withother FOH devices and/or BOH devices, while BOH devices may similarlyidentify and initiate connections with other BOH devices and/or FOHdevices.

In other instances, the techniques described herein may utilize devicelocation within an establishment for issuing instructions or suggestionson the devices. For example, one or more of the devices operating in theexample restaurant, and/or a remote service coupled to these devices,may generate a layout of orders and their respective locations withinthe restaurant and may use this layout for determining when to issueinstructions or suggestions and/or to determine which devices to issuethe instructions or suggestions to. For example, the layout may maintainan association between a first order of a first table associated with afirst location in the restaurant, and a second order of a second tableassociated with a second location in the restaurant, and so forth.

Thereafter, the device(s) and/or the remote service may determine anaction to take regarding one of the orders, such as the first order. Forexample, the device(s) or remote service may determine that thecustomers associated with the first order are likely ready to receivethe bill based on a predefined amount of time having elapsed since theitems associated with the first order were completed and/or delivered tothe customers. After making this determination, the device(s) and/orremote service may determine when an FOH is within a threshold proximityof the first location associated with the first order. For example, thedevice(s) or remote service may determine when a particular FOH deviceis within ten feet of a table that is associated with the first order,based on a GPS signal of the device, based on data from one or morebeacons in the restaurant determining the device's location, and/or thelike.

After determining that the FOH is within the threshold proximity of thefirst location, the device(s) and/or remote service may send, to the FOHdevice, an indication of the suggestion to print the bill for thecustomers associated with the first order. For example, the FOH devicemay present, on a display of the FOH device, a suggestion to print thebill for the first table and an icon that is selectable to cause thebill to be printed (e.g., printed on paper via the FOH device or anotherdevice, printed on a display of the FOH device, or the like).

In another example, the device(s) or the remote service may determine asecond action to take with regard to a second order that is associatedwith a second location within the restaurant. For example, the secondaction may comprise suggesting a certain course to the customers at thesecond location, firing a course for preparation at the BOH of therestaurant (i.e., sending the order to a BOH device), and so forth. Whenthe device(s) or the remote service determines that the same or anotherFOH device is within a threshold proximity of the second location, thatFOH device may receive the suggestion to perform the action and,potentially, an icon that is selectable to perform the action.

By integrating both computational techniques (e.g., for determiningsuggested actions to take with respect to different orders) andproximity-based techniques (e.g., for determining which devices to sendthe suggested actions to), the disclosed methods and systems offerintelligent ways to detect a relevant pair of devices for dedicated and,in some cases, timed communication sessions. That is, these techniquesat least provide technological advancements by sending the notificationsto the appropriate devices, based on their current locations, at theappropriate times, based on the history and timing of the individualorders. The techniques thus result in the sending of communications todevices when the communications are actionable—that is, when theoperators of the devices are near the location where the communicationsare actionable and at times when the communications are actionable.

In still other instances, the techniques described herein may analyzeimage data of an establishment, such as the example restaurant discussedabove, to automatically generate a layout of available seating areas inthe establishment. For example, the techniques may provide a UI fordisplay on a merchant device, instructing the operator of the merchantdevice to use their camera to walk around and image the inside of theestablishment. The merchant device may then analyze this data todetermine the layout or may send this data to another device or remoteservice for analyzing the data. In either case, a device may analyze thedata using light detection and ranging (LIDAR), trained machine-learningmodels, or the like to identify relevant surfaces (such as flatsurfaces) within the establishment. For example, the device may identifyone or more surfaces within the image data that are flat, have apredefined size (e.g., width and length), that are orientedapproximately parallel to a plane defined by a floor of theestablishment, and that are within a predefined length above the planeof the floor (e.g., at least two feet above the floor). Thus, the devicemay analyze the data to identify surfaces that may correspond to seatingareas for customers, such as tables, bar stools, countertops, and thelike. In addition to identifying such surfaces, the device performingthe analysis may determine an associated location (e.g., an X, Ylocation) associated with each respective surface. For example, thedevice may use LIDAR, computer-vision techniques, or the like todetermine the location of each identified surface within the environmentof the establishment.

After analyzing the data to identify seating or ecommerce surfacestherein, the techniques may provide a UI for display on the merchantdevice. In some instances, the UI includes indicators of the identifiedsurfaces overlaid on the actual surfaces in the image data captured bythe merchant device. For example, the UI may overlay a predefined color,cross-hatching, or the like on the identified surfaces overlaid on theimage data of the establishment. The UI may further include aninstruction to the operator of the device to select which of theindicated surfaces correspond to available seating areas. Thus, theoperator of the merchant device may, for example, use a touchscreen orother input mechanism on the merchant device to select those surfacesthat correspond to available seating areas and/or those surfaces that donot, and to allow translation of the virtual layout of the establishmentwith recommended seating and dining surfaces to a physical layout.

After selecting the surfaces that correspond to the available seatingareas, the operator of the merchant device may indicate that they havefinished indicating the available seating areas and may request that alayout of available seating areas be automatically generated. Inresponse to this indication, the merchant device, another device, or theremote service may automatically generate the layout of availableseating areas in the establishment. For example, the device maydetermine the location associated with each surface indicated tocorrespond to a seating area and may use this location and estimatedsize of the surface to generate the layout. In some instances, themerchant may also indicate the number of available seats at each flatsurface (e.g., each table), and the layout may indicate thesecorresponding numbers of seats.

After generating the layout, the layout may be presented on a UI on thedisplay of the merchant device. The presented layout may, for example,comprise a top-down, two-dimensional view of the available seating areasin the establishment. In some instances, this UI may also provide toolsto enable the merchant to modify or correct any errors in the layout.For example, the tools may allow the merchant to move, add, or removetables, seats, and/or the like.

While traditional technology enables merchants to generate a layout ofavailable seating areas manually, the above techniques thus usetechnology on one or more devices to generate image data of anenvironment and automatically generate a layout of available seatingareas in the environment. Thus, these techniques provide an efficientand tailored solution to generating establishment layouts and, further,do so via technological advances. For example, the techniques enable amerchant to generate a layout by capturing image data and allowing oneor more devices to analyze the image data to identify flat surfaces and,based on these flat surfaces, automatically create the layout. Thelayout is thus created automatically, rather than manually, and is donemuch more quickly and efficiently than via manual methods. Furthermore,such layout may be tied to devices to provide some of thefunctionalities disclosed herein. For example, one section displayed inthe layout can be tied to a pair of FOH device and BOH device, whileanother section can be associated with another pair of FOH device andBOH device. Such pre-defined associations can be leveraged whencommunicating for an order, for example.

Additional technical improvements are described below in the discussionof FIGS. 1-82 . It is to be appreciated that while these examples aredescribed with reference to a restaurant environment the techniquesapply equally to other types of merchant and non-merchant environments.

Device-Aware Requests

FIG. 1 illustrates an example architecture 100 for performing techniquesdescribed herein. The example architecture 100 includes a merchantestablishment 102, such as a restaurant, having a front-of-house (FOH)102(1) and a back-of-house (BOH) 102(2). As is known, the FOH 102(1)corresponds to a portion of the establishment 102 where customersinteract with staff of the merchant (e.g., order items, etc.) and caninclude both merchant devices accessible by customers or merchants, orcustomer devices accessible by customers. The BOH 102(2) corresponds toa portion of the establishment 102 where staff prepares items on behalfof the customers and is accessible by merchants. In some instances,staff of the merchant use merchant devices (e.g., devices configured asa point-of-sale (POS) device for conducting transactions with customers,kitchen-display devices for displaying pending orders, etc.), both inthe FOH 102(1) and the BOH 102(2). For example, FIG. 1 illustrates thata user 104(1) may operate a BOH device 106(1), while users 104(2) and104(2) may operate respective FOH devices 106(2) and 106(3). It is notedthat while this example, and examples below, describe the techniques inthe context of a restaurant environment, it is to be appreciated thatthe techniques may apply equally to other retail and non-retailestablishments that may utilize different types of devices (e.g.,BOH/FOH devices and otherwise), such as brick-and-mortar retail stores,warehouses, grocery stores, and/or other retail and non-retailestablishments.

In this example, each of the devices 106(1)-(3) are configured withestablishment applications for performing an array of functions withinthe establishment. For instance, the BOH device 106(1) may be configuredto display details regarding orders associated with respective customersin the FOH 102(1). The BOH device 106(1) may also be configured toestablish communication sessions with other BOH/FOH devices, activateappliances in the establishment, and perform other actions, as describedin detail below. The FOH devices 106(1)-(2), meanwhile, may beconfigured to establish communication sessions with other BOH/FOHdevices, generate orders on behalf of the customers and send the ordersto BOH devices, act as a POS device for conducting transactions with thecustomers, illustrate a layout of available seating areas in theestablishment, and perform other actions, also as described in detailbelow. In some instances, other devices, such as a remote server, mayinitiate communication sessions with BOH and/or FOH devices. Forexample, a remote server may determine when an inventory level isrunning low and may establish a communication session with a BOH deviceto provide a corresponding notification.

In this example, the user 104(1) may use the BOH device 106(1) to viewdetails associated with an order provided to the BOH device 106(1) by aparticular FOH device. Further, in this example, the user 104(1) mayhave a request regarding the order and, thus, may use a UI 108(1) torequest a server who is related to the order, or is proximate to thetable that placed the order. In response to this request, the BOH device106(1) (or another device) may determine an FOH device associated withthe order. That is, the BOH device 106(1) or another device maydetermine, from details associated with the order that the user 104(1)desires clarification on, which FOH device provided the order to the BOHdevice 106(1).

In this example, the BOH device 106(1) may determine that the FOH device106(2) operated by the user 104(2) provided the order and, thus, maygenerate a connection 110 between the BOH device 106(1) and the FOHdevice 106(2). That is, the BOH device 106(1) may initiate and/orestablish a communication session between the BOH device 106(1) and theFOH device 106(2), or vice versa. This communication session maycomprise a connection over a short-range wireless network (e.g.,Bluetooth, Zigbee, etc.), a connection over Wi-Fi, a connection via theInternet, and/or the like. After establishing the connection 110, theBOH device 106(1) or another device may present, on the FOH device106(2), a UI 108(2) indicating a request, such as a clarificationregarding a particular order has been requested by a BOH device. In someinstances, this UI 108(2) may indicate the order for which clarificationis requested, the BOH device 106(1) that initiated the request, thelocation of the BOH device 106(1) in the establishment (e.g., hotstation, cold station, etc.), and/or the like.

Further, while FIG. 1 illustrates presenting the UI 108(2) on the FOHdevice 106(2), in some instances the techniques may additional oralternatively create a near real-time, interactive communication sessionbetween the BOH and FOH devices. For example, the techniques mayestablish a video or voice call, a chat session, or the like between thedevices to enable the user 104(1) to provide input for an order, such asclarify the order with the user 104(2). In some instances, such adedicated session can be timed, for example to lapse after a response tothe original request is obtained or timed to the duration of the order.Furthermore, the request for the user 104(2) can be dynamicallyconfigured with interactive elements (such as buttons) to allow the userto provide input in a frictionless manner. The request can also includealternatives, for example, if the restaurant is running out of inventoryon a specific ordered item.

Using the techniques shown in FIG. 1 , the BOH device 106(1)automatically identifies which FOH device 106(2) provided an order forwhich the user 104(1) has a question and, in response to identifyingthis FOH device, automatically establishes a communication session withidentified FOH device. In some instances, some or all of thesetechniques are performed by applications executing on the BOH/FOHdevices. In other instances, some or all of these techniques areperformed by a remote service 112 communicatively coupled to the BOH/FOHdevices via one or more network(s) 114. The network(s) may represent anycombination of wired and/or wireless networks. Furthermore, as describedherein, a “merchant” can be any entity that offers items (e.g., goods orservices) for purchase or other means of acquisition (e.g., rent,borrow, barter, etc.). The merchant can offer items for purchase orother means of acquisition via brick-and-mortar stores, mobile stores(e.g., pop-up shops, food trucks, etc.), online stores (“ecommerce”),combinations of the foregoing, and so forth. In case of a peer-to-peer(P2P) scenario, the merchant and customer can be a first P2P customerand a second P2P customer, respectively, capable of transferring moneyto each other via a P2P payment application. In some instances, themerchant may also comprise a consumer that purchases one or more items(e.g., using a mobile payment application) and uses the techniquesdescribed herein to finance these items on an individual basis.

In addition, in some instances the establishment 102 may include one ormore network-connected appliances 116 (e.g., “smart appliances”), suchas smart ovens, microwaves, fryers, dishwashers, or the like. In someinstances, these appliances may also communicate with the BOH devices,FOH devices, and/or the remote service 112. For example, the user 104(1)may use the BOH device 104(1) in some instances to turn on or off one ormore of the appliances 116, control the appliances 116, alter settingsof the appliances 116, and/or the like. In some instances, as describedbelow, the BOH device 106(1) may present one or more UIs for notifyingthe user 104(1) when a capacity of one or more of the appliances hasbeen reached and may suggest activation of at least one additionalappliance in response.

In some instances, the remote service 112 may function as a paymentprocessing service that receives and processes payment transactions onbehalf of the establishment 102, as well as on behalf of other merchants118. In this regard, the remote service 112 may receive, from respectivemerchant computing devices associated with a plurality of merchants,respectively, transaction information of transactions performed betweenthe plurality of merchants and a plurality of buyers. For example, theremote service 112 may receive this transaction information from deviceswithin the establishment 102, devices associated with the othermerchants 118, and/or the like. In addition, each of the merchantcomputing devices may have respective instances of a merchantapplication installed thereon for configuring the plurality of merchantcomputing devices as a plurality of point-of-sale (POS) terminals,respectively, with these respective instances of the merchantapplication configuring the respective POS terminals to communicate thetransaction information over one or more networks to the paymentprocessing system (i.e., the remote service 112). In addition, theremote service 112 may generate, using a trained model, a plurality ofmerchant profiles for each of the merchants. The merchant profiles maystore information regarding merchant type, merchant location, merchantinventories, and/or other data associated with the respective merchants.The trained model, meanwhile, may be rained using at least one of theplurality of merchants, the plurality of buyers, the transactioninformation, and/or additional information.

FIG. 2 illustrates example components of the BOH and/or FOH devices 200described herein for performing the technique described herein. Further,while this figure illustrates these components as residing in the FOHand/or BOH devices, it is to be appreciated that some or all of thesecomponents may additionally or alternatively reside in the remoteservice 112 and/or at other locations. As illustrated, each device 200may include one or more processors 202, one or more or more interfaces204 for communicating with other devices, and one or more sensors (e.g.,cameras, GPS units, etc.) for generating data sensor data. In addition,each device 200 may include computer-readable media 206 executing aninstance of an establishment application 210, which may enable thetechniques described above and below. In some instances, a FOH devicemay store and execute an instance of an establishment application 210configured to enable the FOH operations described herein, while a BOHdevice may store and execute an instance of an establishment application210 configured to enable the BOH operations described herein. In otherinstances, the establishment application 210 may be common across bothBOH and FOH devices. The BOH and/or FOH devices may comprise any type ofcomputing device, such as tablet computing devices, mobile phones,laptop computers, desktop computer, server computers, specializedcomputers, and/or the like. In some instances, the FOH device maycomprise a device that is operated by a merchant, while in other devicesthe FOH device may be operated by a customer, such as a customer at atable or other seating area. In still other instances, the FOH devicemay include a first display operable by the merchant and a seconddisplay operable by the customer.

In this example, the establishment application 210 includes anorder-processing component 212, a location-determination component 214,a device-selection component 216, a communication-session component 218,as well as order data 220, location data 222, and analytics data 224.The order-processing component 212 may enable an array of featuresdescribed and illustrated below, such as enabling FOH devices to entercustomer orders, enabling BOH devices to view and interact with orders,and so forth. In general, the order-processing component 212 isresponsible for presenting some or all of each UI illustrated anddescribed below.

The location-determination component 214 may be used to determine alocation of one or more BOH and/or FOH devices for determining one ormore actions to take with respect to these devices. Thelocation-determination component 214 may function to determinelocation(s) of device(s) using GPS data, triangulation techniques basedon beacons or other devices in the establishment 102, or via any otherlocation techniques. In some instances, and as described below, theestablishment application 210 may send UIs to particular devices basedon the location of these devices, as determined by thelocation-determination component 214.

The device-selection component 216 may function to determine whichdevice(s) to establish a communication session between, with thiscommunication session being initiated and/or established via thecommunication-session component 218. In some instances, thedevice-selection component 216 determines which device to establish acommunication session based on a location of one or more devices, basedon which device is associated with a particular order, devicecharacteristics, and/or the like. Further, the communication-sessioncomponent 218 may establish a connection between devices in apeer-to-peer manner, over a wide area network, or a local network,and/or in any other manner. Furthermore, the communication-sessioncomponent 218 may customize the communication session based on therequest, where customization can dictate for example timing for how longthe session should be active, privacy controls with respect toinformation sharing between the devices, and interactive elements basedon the request to allow for seamless interaction. Examples ofestablishing communications between devices for an array of purposes areillustrated and described below, for example at least in FIGS. 3-80 .

The order data 220 may comprise details regarding orders placed to BOHdevice(s) via one or more FOH device(s). For example, the order data 220may comprise identifiers of the ordered items, modifiers of these items,identifiers of a table or location associated with each order,identifiers of a seat or person associated with each item of each order,one or more times associated with each order, a current status of eachorder, and/or the like. This order data 220 may be used for an array ofpurposes, as illustrated and described below.

The location data 222, meanwhile, may be determined by thelocation-determination component 214 and may correspond to the current,past, and/or predicted location(s) of mobile device(s) within theestablishment 102. In some instances, this location data 222 is used todetermine which device(s) to send data to and a time at which to sendthe data to the determined device, as described and illustrated indetail below.

The analytics data 224, meanwhile, may indicate one or more metricsassociated with the operation of the establishment 102. For example, theanalytics data 224 may indicate average times to prepare orders,current, past, or predicted load of certain appliances in the BOH 102(2)of the establishment 102, capacities of these appliances, and/or othertype of metrics that may be tracked in the establishment 102.

FIG. 3 illustrates a flow diagram of an example process 300 forestablishing a communication session, such as between the BOH device106(1) and the FOH device 106(2) of FIG. 1 . The process 300, as well asthe additional processes discussed herein, may be implemented inhardware, software, or a combination thereof. In the context ofsoftware, the described operations represent computer-executableinstructions stored on one or more computer-readable storage media that,when executed by one or more hardware processors, perform the recitedoperations. Generally, computer-executable instructions includeroutines, programs, objects, modules, data structures, and the like thatperform particular functions or implement particular abstract datatypes. Those having ordinary skill in the art will readily recognizethat certain steps or operations illustrated in the figures above may beeliminated, combined, or performed in an alternate order. Any steps oroperations may be performed serially or in parallel. Furthermore, theorder in which the operations are described is not intended to beconstrued as a limitation. In some instances, the processes describedherein may be performed, in whole or in part, by modules of the BOH/FOHdevices, the remote service 112, other devices, and/or combinationsthereof.

An operation 302 represents presenting, on a display of the BOH device106(1), a first UI including details associated with at least a firstorder and a second order. In this example, the FOH device 106(2)provided the first order to the BOH device 106(1), while the FOH device106(3) provided by the second order to the BOH device 106(1). The firstUI may depict details regarding the first order, the second order, and,potentially, other orders provided to the BOH device 106(1) by the sameor other FOH devices.

FIG. 7 illustrates an example of the first UI 700. As illustrated, theUI 700 includes a first order 702(1), a second order 702(2), and, inthis example, six other orders. Each of the illustrated orders mayindicate a particular table or other location in the establishment 102that is associated with the order, the name of the server that providedthe order, and details regarding the order, such as identifiers of theitems, quantities of the items, and so forth. Each order may alsoinclude additional details, such as time at which the order was placed,a time since the order was placed, whether the order is late fordelivery or nearly late, and/or the like. In this example, the FOHdevice 106(2) of FIG. 1 provided the first order 702(1).

Returning to FIG. 3 , an operation 304 represents determining whether aselection is received on the first UI. For example, this operation mayinclude determining whether a touchscreen or other input mechanism onthe BOH device 106(1) has received a selection of a particular order,such as an order displayed on the UI 700. If not, then the process 300continues to the display the first UI at the operation 302. Returning toFIG. 7 , however, the UI 700 illustrates that the user 104(1) of the BOHdevice 106(1) has provided a selection 704 of the first order 702(1). Inthis example, the selection comprises a long-press (e.g., a pressgreater than a threshold amount of time) on the touchscreen of thedevice, while in other instances the selection may comprise any othertype of selection.

An operation 306 of FIG. 3 represents presenting, in response to theselection and on the display of the BOH device 106(1), a second UI thatincludes details (e.g., additional details) of the selected, firstorder. FIGS. 8-9 illustrate respective example UIs 800 and 900 that theBOH device 106(1) may present in response to the selection 704. Forexample, the UIs 800 and 900 illustrate that the first order 702(1) mayexpand on the display of the BOH device 106(1) until reaching the sizeshown in FIG. 9 . In addition to showing details regarding the firstorder 702(1), the UI 900 may also include additional selectable options,such as “print”, “snooze”, or “request server”. The “print” option maybe selectable to print a physical ticket associated with the order,while the “snooze” option may be selectable to pause the order and/ornotifications regarding the order. The “request server” option,meanwhile, may be selectable to request the server that placed theorder.

Returning to FIG. 3 , an operation 308 represents generating, via thesecond UI, a request corresponding to the first order. For example, thisoperation may comprise generating a request in response to the user104(1) selecting one of the selectable options 902 of the example UI900. FIG. 9 , for instance, represents a selection 904 to request theserver that initiated the order. Thus, in this example, the operation308 may generate a request for the server that originated the order.

An operation 310 represents determining that the first FOH device 106(2)originated the first order. For example, the BOH device 106(1) mayanalyze the stored order data associated with the first order 702(1) todetermine that the FOH device 106(2) placed the first order 702(1). Insome implementations, the identification of the FOH device also includesreceiving device characteristics and communication parameters to allowcommunication with the identified FOH device.

An operation 312 represents establishing a communication session betweenthe BOH device 106(1) and the first FOH device 106(2). As describedabove, this may comprise a communication session established over ashort-range wireless network, Wi-Fi, the Internet, and/or any otherwired and/or wireless connections. Also as described above, the BOHdevice 106(1) may automatically determine the FOH device 106(2) thatoriginated the order and may automatically establish the communicationsession in response to receiving the selection from the user 104(1).

At an operation 314, an indication of the request is sent to the FOHdevice 106(2) via the established communication session. For example,the indication may comprise a notification that the user 104(1)associated with the BOH device 106(1) has a question regarding an order(or, specifically, the first order 702(1)), a specific query regardingthe order, or the like. Further, in some instances the communicationsession may enable a real-time dialogue between the respective users104(1) and 104(2).

FIG. 10 illustrates an example UI 1000 that the FOH device 106(2) maypresent in response to receiving the indication of the request. Asillustrated, the UI 1000 may include a notification 1002 indicating thatthe kitchen has requested clarification regarding a particular table inthe establishment 102. In addition to identifying the table (or otheridentifier of the order), the notification 1002 may indicate a physicallocation of the BOH device 106(1) from which the request originated. Forinstance, in this example the notification 1002 indicates that therequest was initiated from the “hot station”. In some instances, thenotification 1002 may further indicate a query from the user 104(1)(e.g., “Should the sauce be on the side?”) and/or other information.

FIG. 4 illustrates a flow diagram of another example process 400 forestablishing a communication session between a BOH device and an FOHdevice in the establishment 102 of FIG. 1 . In this example, thecommunication session may be established for sending, to the FOH device,an indication that an item associated with an order placed by the FOHdevice has been prepared.

An operation 402 represents presenting, on a display of the BOH device106(1), a UI including details regarding an order. FIG. 11 , forinstance, illustrates an example UI 1100 illustrating details regardingorders 1102(1), 1102(2), and so forth.

An operation 404 represents determining whether the BOH device 106(1)has received an indication that an item from the order has beenprepared. FIG. 11 , for example, illustrates that the user 104(1) of theBOH device 106(1) has provided a selection 1104 of a particular item(“Hudson Salad”) of the display order. In some instances, this selection1104 may comprise a long-press on the touchscreen of the BOH device106(1).

FIG. 12 illustrates that, in response to this selection 1104, the BOHdevice 106(1) may present an UI 1200. As illustrated, the UI 1200includes a menu 1202 of multiple options to request regarding theselected item, including “Complete Item”, “Make Now”, “Send To . . . ”,and “Close”. While not illustrated, selection of the “Complete Item”icon may result in the BOH device 106(1) determining, at the operation404, that the BOH device 106(1) has received an indication that an itemfrom the selected order has been completed. Selection of the “Make Now”icon, meanwhile, may result in a communication session being establishedwith another BOH device, as described below with reference to FIGS.13-15 , while selection of the “Send To . . . ” icon may move the job ofpreparing the item to another station. Selection of the “Close” icon mayclose the menu 1202.

In this example, the user 104(1) may select the “Complete Item” optionin the menu 1202 and, in response, the BOH device 106(1) may determinethat it has received an indication that an item has been prepared.Returning to FIG. 4 , an operation 406 represents determining that aparticular FOH device originated the order associated with the item hasbeen completed. Again, this operation may comprise analyzing the orderdata 220 associated with the order to identify the FOH device thatprovided the order to the BOH device 106(1).

An operation 408 represents establishing a communication session withthe FOH device determined at the operation 406. As described above, thismay comprise a communication session established over a short-rangewireless network, Wi-Fi, the Internet, and/or any other wired and/orwireless connections. Again, the BOH device 106(1) may automaticallydetermine the FOH device that originated the order and may automaticallyestablish the communication session in response to receiving theselection from the user 104(1).

At an operation 410, an indication that the item has been prepared issent to the FOH device via the established communication session. Forexample, the indication may comprise a notification that a particularitem has been completed, that each item in the order has been completed,or the like. Thus, the operator of the corresponding FOH device may stayapprised of the progress of each order he or she is responsible for.FIGS. 21-22 and a corresponding discussion illustrate and describe thisin further detail below.

FIG. 5 illustrates a flow diagram of another example process 500 forestablishing a communication session between a BOH device and an FOHdevice for sending, in this example, an indication that a user has begunpreparing an item associated with an order placed by the FOH device.

An operation 502 represents presenting, on a display of the BOH device106(1), a UI including details regarding an order. FIG. 11 , forinstance, illustrates the example UI 1100 illustrating details regardingthe orders 1102(1), 1102(2), and so forth.

An operation 504 represents determining whether the BOH device 106(1)has received an indication that a user has begun preparing an item ofthe order. FIG. 11 , for example, illustrates that the user 104(1) ofthe BOH device 106(1) has provided a selection 1104 of a particular item(“Hudson Salad”) of the display order. In some instances, this selection1104 may comprise a long-press on the touchscreen of the BOH device106(1).

FIG. 12 illustrates that, in response to this selection 1104, the BOHdevice 106(1) may present an UI 1200. As illustrated, the UI 1200includes the menu 1202 of the multiple options. In addition, to theillustrated options, this menu 1202 (or other menus on other UIsillustrated and described herein) may include an option to indicate theitem has been started. In this example, the user 104(1) may select the“Starting Item” option and, in response, the BOH device 106(1) maydetermine that it has received an indication that a user has begunpreparing a particular item. Returning to FIG. 5 , an operation 506represents determining that a particular FOH device originated the orderassociated with the item has been completed. Again, this operation maycomprise analyzing the order data 220 associated with the order toidentify the FOH device that provided the order to the BOH device106(1).

An operation 508 represents establishing a communication session withthe FOH device determined at the operation 506. As described above, thismay comprise a communication session established over a short-rangewireless network, Wi-Fi, the Internet, and/or any other wired and/orwireless connections. Again, the BOH device 106(1) may automaticallydetermine the FOH device that originated the order and may automaticallyestablish the communication session in response to receiving theselection from the user 104(1).

At an operation 510, an indication that the item has been prepared issent to the FOH device via the established communication session. Forexample, the indication may comprise a notification that a user in theBOH 102(1) has begun preparing a particular item. Thus, the operator ofthe corresponding FOH device may stay apprised of the progress of eachorder he or she is responsible for. Again, FIGS. 21-22 and acorresponding discussion illustrate and described this in further detailbelow.

FIG. 6 illustrates a flow diagram of another example process 600 forreceiving a request to activate an appliance to handle a currentcapacity of orders. For example, this process 600 may occur when acapacity of one or more of the appliances 116 of FIG. 1 have beenreached or is predicted to be reached shortly.

As illustrated, an operation 602 represents presenting, on a display ofthe BOH device 106(1) a UI indicating: (i) that a current or predictednumber of orders handled by a first appliance is different from acapacity of the first appliance, and (ii) a suggestion toactivate/deactivate a second appliance to load balance the current orpredicted number of orders handled by the first appliance. For example,the BOH device 106(1), the remote service 112, and/or another device maydetermine, from the order data 220 and the analytics data 224, that anumber of items or orders being handled by the first appliance isgreater than the capacity of the first appliance or is expected to begreater than the capacity of the first appliance within a thresholdamount of time. In response, the BOH device 106(1) may present the UIindicating the number of orders and the suggestion to activate thesecond appliance.

FIG. 17 , for instance, illustrated an example UI 1700 that includes anindication 1702 of a number of tickets (or orders) currently beinghandled by a first fryer in the establishment 102, a number of ticketscurrently being handled by a second fryer in the establishment 102, anda suggestion to activate a third fryer. For instance, the UI 1700indicates that the first fryer currently has 32 tickets (nearly at itscapacity), while the second fryer currently has 23 tickets (and is atits capacity). In addition, the UI 1700 may include different coloring,hatching, or other visual indicia to indicate the number or relativeamount of the tickets that are currently late, predicted to be late,timely, and/or the like.

In addition, the UI 1700 further includes an icon 1704 (“ActivateStation”) that, when selected may result in the activation of the thirdfryer. For example, upon selection of the icon 1704, the BOH device106(1) may send a request to activate the third fryer directly to thethird fryer, to the third fryer via the remote service 112, or in anyother manner. In response to receiving this request, the third fryer mayactivate, which may include turning on, altering its settings (e.g.,heat), and/or the like. In addition, upon activation of the third fryer,tickets currently in queue with the first or second fryers mayautomatically move from these queue(s) to a queue associated with thethird fryer. In some instances, each fryer or other appliance may beassociated with a corresponding display and, thus, the display of thethird fryer may be turned on when the fryer is activated. Further, thedisplays of the first, second, and third fryers may be updated uponactivation of the third fryer to indicate the tickets that each fryer isnow responsible for. Further, while some of the above examples describesuggesting that a user activate an appliance or other IOT device, suchas a fryer, in other instances the techniques may automatically activateone or more of these appliances/devices based on certain criteria beingmet. For example, when the currently active fryers become associatedwith a predefined number of orders or exceed their capacity, one or moreadditional fryers may be automatically activated, and orders previouslyassigned to the currently active fryers may be reassigned to the newlyactivated fryer(s).

Returning to FIG. 6 , an operation 604 represents determining whetherthe BOH device 106(1) has received a selection of the icon to activatethe second appliance. For example, this operation may includedetermining whether the user 104(1) of the BOH device 106(1) hasselected the icon 1704 for activating the third fryer shown in FIG. 17 .If no selection is received, then the process 600 continues to displaythe UI at the operation 602.

If the selection is received, however, then an operation 606 representscausing activation of the second appliance at least partly in responseto the selection. Causing activation of the second appliance may includeturning on the second appliance, altering settings of the secondappliance, turning on a display associated with the second appliance,and/or the like.

After activating the second appliance, an operation 608 representspresenting, on the display of the BOH device 106(1), a UI indicating anumber of orders to be prepared using the first appliance and/or anumber of orders to be prepared using the second appliance. Forinstance, this operation may include updating one or more displays toindicate the number of orders that each appliance is now responsiblefor. In some instances, this includes updating the display of a BOHdevice at an expeditor station, while in other instances it may includeupdate the display associated with the first appliance and the displayassociated with the second appliance.

FIG. 18 , for instance, illustrates a UI 1800 that the BOH device 106(1)may present in response to the user 104(1) selecting the icon 1704 onthe UI 1700 presented on the display of the BOH device 106(1). Asillustrated, the UI 1800 includes an indication 1802 that the icon 1704was selected and, thus, the third fryer has been activated.

FIG. 19 illustrates a subsequent UI 1900 that the BOH device 106(1) maypresent after presenting the UI 1800. As illustrated, the UI 1900indicates, at 1902, that tickets previously assigned to the first andsecond fryers have been re-assigned to the third fryer. Thus, at thisexample moment, the first fryer is now responsible for 21 tickets, thesecond fryer for 14 tickets, and the third fryer for 18 tickets.Importantly, this portion of the UI 1900 indicates that none of thethree fryers have reached their capacity. By determining when theappliances are at or about to reach capacity, suggesting activation ofan additional appliance, and activating the appliance upon receiving arequest to do so, the techniques described herein thus enable theestablishment to avoid becoming overwhelmed and late with their receivedorders.

As described above, FIG. 7 illustrates the example UI 700 that a BOHdevice may display for presenting current orders that are to beprepared. Again, the UI 700 illustrates eight orders in this example,such as the first order 702(1), the second order 702(2), and so forth.The UI 700 further displays details regarding each order, such as theitems of the order, modifiers associated with the order, a server thatplaced the order, a time associated with the order (e.g., elapsed timesince the order was placed, and/or the like. In some instances, the UI700 may be presented on a BOH device at an expeditor station in the BOH102(2), a hot station in the BOH 102(2), a cold station in the BOH102(2), and so forth. In this example, the UI 700 indicates that a userof the BOH device provides the selection 704 of the first order 702(1).

FIG. 8 illustrates the example UI 800 that the BOH device may display inresponse to the selection 702. As illustrated, the selected order 702(1)is expanding to present additional details regarding the order andoptions regarding the order. FIG. 9 illustrates the example UI 900 thatcontinues the animation that may occur on the display of the BOH devicein response to the selection 702. As illustrated, the UI 900 may displayadditional details regarding the first order 702(1) and, further, maydisplay the selectable options 904 for the operator of the BOH device,including an option to request a server that placed the order. Asdescribed above, in this example, the operation of the BOH device mayselect the option to request the server that originated the order.

FIG. 10 illustrates the example UI 1000 that an FOH device thatoriginated the first order 702(1) may display in response to theselection 904 from the UI 900. As illustrated, the UI 1000 may includethe notification 1002 that the operator of the BOH device has requestedclarification regarding a particular order. In some instances, thenotification 1002 may include details regarding the query, an indicationof the location of the BOH device, and/or additional details.

FIG. 11 illustrates the example UI 1100 that a BOH device associatedwith an expeditor station may display. As illustrated, the UI 1100includes details regarding four orders, including the first order1102(1), the second order 1102(2), and so forth. Here, the operator ofthe BOH device provides the selection 1104 regarding a particular itemassociated with the order 1102(1).

FIG. 12 illustrates the example UI 1200 that the BOH device associatedwith the expeditor station may display in response to the selection1104. As illustrated, the UI 1200 presents a menu 1200 that includesseveral options from which the operator may select from. These optionsmay include an option to indicate that the item has been completed orprepared (“Complete Item”), an option to send a request to another BOHdevice or station to begin preparation of the item (“Make Now”), anoption to send information regarding the preparation of the item toanother BOH device or station (“Send To . . . ”), and so forth. In thisexample, the operator of the BOH device at the expeditor stationprovides the selection 1204 to request that an operator associated withanother BOH device and station begin preparing the item.

For example, selection of this option may cause the BOH device at theexpeditor station to automatically establish a communication sessionwith a BOH device at a station that is responsible for preparing thisitem. In one example, the BOH device shown in FIG. 12 may automaticallyanalyze the order data 220 to determine the BOH station responsible forpreparing this item, which may be based on the type of the item, currentload at BOH stations in the establishment 102, and so forth. In thisexample, the BOH device of FIG. 12 may determine that because the itemis a salad, the request to make the item now is to be routed to a coldstation in the BOH 102(2). Thus, the BOH device of FIG. 12 mayautomatically establish a communication session with a BOH device at thecold station and send the request to begin preparation of the salad.

FIG. 13 an example UI 1300 that a BOH device at the cold station maydisplay prior to the selection 1204 at the expeditor station shown inFIG. 12 . As illustrated, this UI 1300 may illustrate orders and itemswithin the orders that are to be prepared. In addition, the UI 1300 mayprioritize preparation of different orders in the establishment based onwhen the orders were provided by FOH devices, and the like. Asillustrated, the UI 1300 includes details regarding a first order1302(1), a second order 1302(2), and so forth.

FIG. 14 illustrates an example UI that the BOH device of FIG. 13 maydisplay after the selection 1204 at the expeditor station shown in FIG.12 . As illustrated, this UI 1400 includes a notification 1402 that theexpeditor has requested that the preparation station begin preparing acertain item. For example, the notification 1402 may appear at the topof the UI 1400 and may indicate, for example, the location of the tableor order for which preparation of an item is being requested. Inaddition, the notification 1402 may include a selectable icon (“StartOrder”) that the operator of the BOH device may select to beginpreparation of the item. As shown below, this may automaticallyreprioritize the orders illustrated on the BOH device at thispreparation station. As illustrated, in this example the operator of theBOH device provides a selection 1404 of the selectable icon.

FIG. 15 illustrates an example UI 1500 that the BOH device of FIG. 13may present after the operator of the BOH device provides the selection1404 shown in FIG. 14 . As illustrated, the displayed orders have beenreprioritized in response to this selection 1402. For example, a neworder 1502 corresponding to the order for which the expeditor stationrequested to be “made now” may be displayed first, while the order1302(1) may now be presented second, the order 1302(2) may be presentedthird, and so forth. Thus, the order for which the expeditor requestedto be made now may be presented in the location of the UI 1500corresponding to the most order that is first in line (that is, the mosturgent orders). In addition, the UI 1500 includes an indication 1504that the order is fact to be made now (“Make Now”).

FIG. 16 illustrates another example UI 1600 that a BOH device maydisplay. Here, the UI 1600 presents various kitchen-performance metrics,which may be displayed at an expeditor station, at a preparationstation, a sequencing station, or the like. In some instances, the BOHdevices may present different metrics based on a currently assigned roleof each BOH device. For example, a BOH device at a hot station maypresent metrics corresponding to fryer wait times, oven wait times, andthe like, while a BOH device at a cold station may present metricscorresponding to average times to prepare salads, and the like. Inanother example, a BOH device at an expeditor station may presentmetrics associated with orders as a whole, such as average times todeliver completed orders to tables, orders that are running late orpredicted to run late, or the like.

In this example, the UI 1600 presents example metrics 1602, whichinclude the average time to prepare an order, the station that iscurrently the slowest in the kitchen, and the item that is currentlytaking the longest to prepare. In addition, the example metrics 1602indicate the number of tickets that are over time by certain amounts oftime (e.g., more than ten minutes late, more than five minutes late,etc.). The example metrics 1602 further depict the currently load atcertain stations, such as a current number of tickets that are assignedto a first fryer, a second fryer, and so forth. In addition, the metrics1602 may indicate the number of tickets that are currently late at eachfryer or other station, the number of tickets that may be late at eachfryer and other station, and so forth. Of course, while the metrics 1602illustrate example metrics, it is to be appreciated that any other typesof metrics may be stored in the analytics data 224 and presented on theUI 1600 and/or other UIs.

FIG. 17 illustrates the example UI 1700 that the BOH device may display,as discussed above. Here, the UI 1700 presents certain suggestions 1702for operation of the establishment, such as a suggestion to activate anadditional fryer station. This UI 1700 also includes the icon 1704 forautomatically activating the suggested fryer station.

FIG. 18 illustrates the example UI 1800 that the BOH device may displayafter the operator of the device selects the icon 1704. As describedabove, in response to this selection, the UI 1800 may change the displayof the icon from “activate station” to “activated”. In addition, the BOHdevice may have automatically sent a request to activate to the thirdfryer station in response.

FIG. 19 illustrates the example UI 1900 that the BOH device may displayafter the third fryer station has bene activated. As illustrated, the UI1900 indicates, at 1902, that the tickets being handled by the fryershave been reallocated based on the activation of the third fryer. Forexample, the UI 1900 illustrates that the load has now been balancedacross the three fryers such that no individual fryer is currentlyresponsible for a number of orders that is greater than the respectivecapacity of the fryer. Further, while the UIs 1700, 1800, and 1900collectively illustrate the activation of a fryer, it is to beappreciated that any other type of connected appliances may beautomatically activated (or suggested to be activated) in otherinstances.

FIG. 20 illustrates another example UI 200 that a BOH device in theestablishment 102 of FIG. 1 may display. Here, the UI 2000 presentsdetails regarding example orders 2002(1), 2002(2), and 2002(3). Inaddition, the UI 2000 presents a selectable icon 2004 (“Start Order”)that, when selected, may reprioritize the orders displayed on the UI,may reprioritize orders displayed on other BOH devices, and/or may senda notification that an order has begun being prepared to an FOH devicethat is associated with the order.

FIG. 21 , for example, illustrates an example UI 2100 that an FOH devicemay present for informing an operator of the FOH device of the currentstatus of orders that the operator has placed to the BOH. That is, theUI 2100 may present the current status of each order that the server whois logged in to the FOH device has placed to the BOH 102. In thisexample, the UI 2100 indicates, at 2102, that the order associated withtable 12 is ready, meaning that the server may deliver or may requestthat another user acquire the items associated with the order from theBOH 102(2) and deliver the items to table 12 in the FOH 102(1). Inaddition, the UI 2100 indicates, at 2104, that the order for table 4 isnearly complete (as 3 of 4 items are completed), while indicating, at2106, that half of the order is complete for the order associated with“Dining 4”. In some instances, the UI 2100 may periodically update asitems are marked as completed via BOH devices(s). Further, in someinstances, the FOH device may present a pop-up notification or the likewhen an order is complete, when an item of an order is complete, and soforth.

The UI 2100 may include additional details regarding orders placed bythe server operating the FOH device. For example, the UI 2100 mayindicate, at 2108, the number and identity of tables currently beinghandled by the server and, at 2110, items (or “courses”) that arecurrently being held, and so forth.

FIG. 22 another example UI 2200 that an FOH device may display toprovide additional information to server operating the FOH device. Forinstance, in addition to the information described above with referenceto FIG. 21 , the UI 2200 may present information regarding a currentinventory at the establishment 102. For example, the UI 2200 mayindicate, at 2202, items that are currently unavailable (e.g., becausethey have sold out) and, at 2204, items that are currently running low.Of course, while a few example inventory details are shown in the UI2200, it is to be appreciated that any other details, metrics, or thelike may be presented.

Routing Requests Based on Contextual Information

FIG. 23 illustrates the example architecture 100 introduced in FIG. 1 .In this example, requests to perform certain actions may be sent to themost relevant FOH device, where relevance can be determined based oncontextual information, such as the location of the FOH devices in theestablishment 102, as well as based on current statuses of orders withinthe establishment 102 and the location associated with these orders. Inanother information, contextual information can be derived from time ofthe day, past history of the communication sessions, a location of theFOH device with respect to the location of the order, ranking of the FOHdevice with respect to other devices (in case of multiple devices, thedevices may be ranked in priority); and historical data with respect tothe first device (for example, for certain requests, a specific FOHdevice may be activated for assistance), and so on.

FIG. 23 , for instances, illustrates that the FOH device 106(2) operatedby the user 104(2) is currently located a certain distance 2302 from alocation 2304 in the establishment 102 that is associated with aparticular order associated with example customer 2316. For instance,when the user 104(2) opened an order for the customer 2316 using the FOHdevice 106(2), the user 104(2) may have indicated that the customer (andthus the associated order) is seated at a particular bar seat that isassociated with the illustrated location 2304. Thus, in some instances,the FOH device 106(2) may present information regarding the order of thecustomer 2316 when the FOH device 106(2) is determined to be within athreshold distance of the location 2304.

In the illustrated example, for instance, the distance 2302 between theFOH device 106(2) and the location 2304 may be within the thresholdproximity. Further, the FOH device, a BOH device, the remote service 112and/or another device may determine that there are one or more currentactions that may need to be taken with regard with the order of thecustomer 2316. For example, based on a time associated with the order(e.g., elapsed time, time since a course was served, etc.), one or moreof the devices may determine that it is time to offer the bill thecustomer 2316, ask if the customer 2316 would like desert, check on thecustomer 2316, and/or the like. In the illustrated example, it isdetermined that it may be time to print the bill the for the customer2316. Thus, in response to determining that the FOH device 106(1) iswithin the threshold proximity of the location 2304, the FOH device106(1) may present an example 2306 suggesting that the user 104(1) printthe bill for the user. In addition, the UI 2306 may include a selectableicon to print the bill.

In another example, the FOH device 106(2) may currently reside a certaindistance 2308 from a location 2310 that is associated with an order aparticular table 2318 in the establishment. Further, the FOH device, aBOH device, the remote service, and/or another device may determine thatthis distance 2308 is less than a threshold distance. Further, one ormore devices may determine an action that may need to be taken withregards to the order associated with the table 2318. Thus, in responseto determine that the FOH device 106(2) is within threshold distance ofthe location 2310, the FOH device 106(2) may present an example UI 2312that suggests that the user 104(2) perform a certain action. In thisexample, the UI 2312 may suggest that the user 104(2) fire an orderedcourse for the users at the table 2318. For example, it may bedetermined that a predefined amount of time has elapsed since a certainevent (e.g., since serving an appetizer) and, thus, it is time to firethe next course to the BOH 102(2).

The location-determination component 214, described above, may determinethe current locations of the FOH devices in any suitable manner. In someinstances, the FOH devices utilize GPS sensors that periodically orcontinually report out their current location. In other instances, theestablishment 102 includes one or more beacons, such as example beacons2314(1), 2314(2), and 2314(3), which may be used by the FOH devices fortriangulating their current location in the establishment 102. Forexample, each FOH device may measure a respective signal strengthbetween the FOH device and each of the beacons 2314(1)-(3), each ofwhich may be associated with a predefined location, for triangulating acurrent position of the FOH device. In one example, the beacons can bewireless beacons. Of course, while a few example location-determinationtechniques are described, it is to be appreciated that the respectivelocations of the FOH devices may be determined in any other manner.

The above techniques may thus suggest certain actions to FOH devicesbased on current statuses of orders within the establishment 102 andbased on current or predicted locations of the FOH devices within theestablishment. For example, as the users traverse the establishment 102,the respective displays of the FOH devices may be updated to suggestcertain actions that are pertinent to orders that are associated withlocations that the operators of the devices are currently near. Forinstance, while the above examples describe suggesting to print a billand fire a course, other suggested actions may include suggesting toopen a table when an operator is near a table that is not currentlyassociated with an order, suggesting to check on customer(s) when near atable that received their entrees five minutes prior, and the like.

In another example, the location-determination component 214 maydetermine whether tables move within the establishment and may, inresponse, update a UI indicating a current layout of the establishment.For example, if a customer or employee of the establishment moves afirst table, having a first beacon coupled thereto, nearer a secondtable, having a second beacon coupled thereto, the locationdetermination component may determine that the first table has movednearer the second table based on the altered signal strength. Inresponse, the UI indicating the current layout of the establishment maybe updated to indicate this change.

FIG. 24 illustrates a flow diagram of an example process 2400 fordetermining that a particular FOH device is relevant to a particularorder based on context information, with the context information beingbased on the device being within a threshold proximity of a firstlocation associated with the order, the device being ranked higherregarding the order than other devices, and/or historical data regardingthe device (e.g., the device having previously interacted with theorder). In response, the process may send a UI to the FOH devicerequesting or suggesting a particular action associated with the firstlocation.

An operation 2402 represents generating a layout of an establishmentindicating that a first order is associated with a first location and asecond order is associated with a second location. In some instances, aFOH device, a BOH device, another device in the establishment, and/or aremote service may generate and maintain this layout. For example, thisdevice may store an association between tables and other seating areasin the establishment and the respective locations of these tables andother seating areas within the establishment. For example, a first table(T1) may be associated with a particular X, Y location in theestablishment, while a second table (T2) may be associated with anotherX, Y location and a bar seat (B1) may be associated with yet another X,Y location, and so forth.

An operation 2404 represents determining an action to take regarding thefirst order based at least in part on a current status of the firstorder. For example, the order-processing component 212 may determine,from the order data 220, trigger data that indicates that a certainaction may need be taken with regards to the first order. For example,the order-processing component 212 may determine, from the order data220, that a threshold amount of time has elapsed from a certain event(e.g., the opening of the order, the serving of a previous course,etc.), which may trigger suggestion of an occurrence of a certain action(e.g., suggesting to print a bill, suggesting a next course, etc.).Thus, the order-processing component 212 may determine an action thatmay need to be taken with regard to the first order based at least inpart on the current status of the first order.

An operation 2406 represents determining whether an FOH device in theestablishment is within a threshold proximity of the first locationassociated with the first order. If not, then the process 2400 may awaituntil an FOH device is within the threshold proximity. In someinstances, this operation may comprise determining whether theparticular FOH device that is associated with the first order is withinthe threshold proximity of the first location, while in other instancesthis operation may comprise determining whether any FOH device is withinthe threshold proximity.

If the operation 2406 determines that an FOH device is within thethreshold proximity of the first location, then an operation 2408represents generating a UI indicating the action to take regarding thefirst order, while an operation 2410 represents sending the UI fordisplay on the FOH device. FIG. 31 , for example, illustrates an exampleUI 3100 that the FOH device may present in response to being locatedwithin the threshold proximity of the first location associated with thefirst order. As illustrated, the UI 3100 may include a menu thatidentifies the table or order, as one or more suggested actions 3102 totake regarding the order. In this example, the menu 3102 suggests thatthe operator of the FOH device continue printing a bill for thecustomer(s) associated with the first order. The UI 3100 may alsoinclude an icon 3104 that is selectable to perform the suggested action.In some instances, the FOH device may generate the UI, while in otherinstances the remote service 112, a BOH device, or another device maygenerate the UI for presentation on the display of the FOH device.

FIG. 25 , meanwhile, illustrates a flow diagram of an example process2500 that may occur with regards to the second order that is associatedwith the second location, as described above with reference to theoperation 2402. Here, an operation 2502 represents determining an actionto take regarding the second order based at least in part on a currentstatus of the second order. For example, the order-processing component212 may determine, from the order data 220, trigger data that indicatesthat a certain action may need be taken with regards to the secondorder.

An operation 2504 represents determining whether an FOH device in theestablishment is within a threshold proximity of the second locationassociated with the second order. If not, then the process 2500 mayawait until an FOH device is within the threshold proximity. Again, insome instances, this operation may comprise determining whether theparticular FOH device that is associated with the second order is withinthe threshold proximity of the second location, while in other instancesthis operation may comprise determining whether any FOH device is withinthe threshold proximity.

If the operation 2504 determines that an FOH device is within thethreshold proximity of the first location, then an operation 2406represents generating a second UI indicating the action to takeregarding the second order, while an operation 2508 represents sendingthe UI for display on the FOH device. FIG. 32 , for example, illustratesan example UI 3200 that the FOH device may present in response to beinglocated within the threshold proximity of the second location associatedwith the second order. As illustrated, the UI 3200 may include a menuthat identifies the table or order, as one or more suggested actions3202 to take regarding the order. In this example, the menu 3202suggests that the operator of the FOH device “fire course 2” for thecustomer(s) associated with the second order. The UI 3200 may alsoinclude an icon 3204 that is selectable to perform the suggested action.In some instances, the FOH device may generate the UI, while in otherinstances the remote service 112, a BOH device, or another device maygenerate the UI for presentation on the display of the FOH device.

FIG. 26 illustrates a flow diagram of another example process 2600.Here, an operation 2602 represents determining whether an FOH device iswithin a threshold proximity of a third location in the establishmentthat is associated with a table or other seating area that is notcurrently associated with an open order. That is, this operation maycomprise determining whether a user associated with an FOH device iswalking by or otherwise near a table or seating area that is currentlynot associated with an open order or ticket.

If so, then an operation 2604 represents generating, at least partly inresponse to determining that the FOH device is within the thresholdproximity of the third location, a third UI suggesting that a thirdorder associated with the third order be opened. An operation 2606represents sending this UI for presentation on the display of the FOHdevice. FIG. 33 , for instance, illustrates an example UI 3300 that theFOH device may present in response to being within a threshold proximityof the third location that is not currently associated with an openorder. As illustrated, the UI 3300 may include a menu that identifiesthe table or order, as one or more suggested actions 3302 to takeregarding the order. In this example, the menu 3302 suggests that theoperator of the FOH device open the table such that the operator maybegin placing an order for customers that are or will be seating at thetable or other seating area. The UI 3300 may also include an icon 3304that is selectable to perform the suggested action. In some instances,the FOH device may generate the UI, while in other instances the remoteservice 112, a BOH device, or another device may generate the UI forpresentation on the display of the FOH device.

FIG. 27 illustrates a flow diagram of another example process 2700 forenabling an operator of the FOH device to add items to an order. Anoperation 2702 represents presenting, on a display of the FOH device, afourth UI that includes: (i) respective icons corresponding to itemsoffered in the establishment, and (ii) the layout of tables and otherseating areas in the establishment. FIG. 34 , for instance, illustratesan example UI 3400. As illustrated, this UI 3400 includes example icons3402 of items offered in the establishment and the layout 3404 of tablesand other seating areas in the establishment.

Returning to FIG. 27 , an operation 2704 comprises determining whether auser input to add a first item to a first order (associated with a firstseating area on the layout) is received. For example, this operation maycomprise determining whether a user input is received that begins at alocation on the display corresponding to an icon associated with thefirst item and ending at a location on the display corresponding to alocation on the layout that is associated with the first order.

FIG. 34 , for example, illustrates that an operator the FOH device hasprovided a selection 3406, such as a press on a touchscreen of the FOHdevice. FIG. 35 , meanwhile, illustrates a UI 3500 that includes theoperator dragging the icon for the item (“Chips and Guac”) towards thelayout 3404 of the establishment. FIG. 36 illustrates an example UI 3600in which the operator “drops” the icon on an icon 3602 on the UI 300corresponding to a particular table (“table 2”) of the layout 3404.

Returning to the process 2700, an operation 2706 represents adding thefirst item to the first order in response to receiving the user input atthe operation 2704. That is, the first item may be added to the firstorder after the user drops the icon corresponding to the item on theicon 3602 corresponding to the table, as shown in FIG. 36 .

In addition, an operation 2708 represents setting a time for apredefined amount of time. In some instances, this may comprise settinga timer for an amount of time, after which the item(s) associated withthe order will be “fired” (i.e., sent to a BOH device for preparation).That is, after adding the first item to the first order, a timer may setand, upon expiration of the timer, the first order may be sent forpreparation. FIG. 37 , for instance, illustrates an example UI 3770 thatinclude a timer 3702 set for a predefined amount of time (in thisexample, 20 seconds) in response to the item icon being dragged anddropped onto the icon 3602 associated with the table.

An operation 2170, meanwhile, represents determining whether a userinput is received to add a second item to the first order. FIG. 38 , forinstance, illustrates the operator of the FOH device selecting an icon3802 corresponding to a second item (“Bud Bucket”) and dragging anddropping the icon 3802 onto the icon associated with the same table.FIG. 38 also illustrated that the timer 3702 has counted down to fifteenseconds since the adding of the first item to the order.

An operation 2712 represents adding the second item to the first orderin response to the second user input. In addition, an operation 2714represents re-setting the timer to the predefined amount of time. FIG.39 , for instance, illustrates an example UI 3900 that indicates thatthe timer 3702 has been re-set to the original twenty seconds.

An operation 2716, meanwhile, represents determining whether a userinput has been received at the location on the display corresponding tothe first location that is associated with the first order. For example,this operation may determine whether a user input is received on theicon corresponding to the table or other seating area that is associatedwith the first order. FIG. 39 , for instance, illustrates an operatorproviding a selection 3902 of the icon corresponding to the tableassociated with the example order.

If the operation 2716 determines that the user input is received, thenan operation 2718 represents presenting, on the display of the FOHdevice, an icon for submitting the first order, including the first andsecond items, to the BOH prior to expiration of the predefined amount oftime. FIG. 40 , for example, illustrates an example UI 4000 thatincludes a menu 4002 including an icon 4004 (“Fire Now”) to enable theoperator to send the order directly to the BOH 102(2) prior toexpiration of the timer 3702. In addition, the menu 4002 includes anicon for canceling the items in this example.

FIG. 28 illustrates a flow diagram of another example process 2800 fordetermining an item to suggest for addition to a first order andpresenting the suggestion on an FOH device in response to the FOH beingwithin a threshold proximity of a first location associated with thefirst order. An operation 2802 represents determining an item to suggestfor addition to the first order. For example, the FOH device, a BOHdevice, the remote service 112, or another device may determine an itemto suggest to the first order based on any number of criteria, such asthe items currently in the order, the history of items ordered by thecustomers associated with the first order, a current time of day, acurrent special in the establishment, or the like.

An operation 2804 represents determining whether an FOH device is withina threshold proximity of the first location associated with the firstorder. As described above, this operation may be based on thelocation-determination component 214 determining, using the locationdata 222, whether any FOH device (or an FOH device associated with thefirst order) is within a threshold proximity of the first location. Ifthen, then an operation 2806 represents sending, to the FOH device, afifth UI that includes the suggestion to add to the suggested item tothe first order. In some instances, this suggestion, and othersuggestions described herein, may be based on prior behavior of one ormore customers, such as a purchase history of a particular customer towhom the suggestion is being presented, prior purchases of othercustomers, and/or the like. In some instances, the remote service 112described above may generate some or all of these suggestions.

FIG. 41 , for instance, illustrates an example UI 4100 that includes, at4102, an indication of a table and, at 4104, suggested items and otheractions for that table. For instance, in this example, a suggested itemof “Bug Light Bucket” and a suggested item of “Fries” is determined forthe order that is currently associated with the “Chef's Table”. Thus,upon the FOH device being located within the threshold proximity of theChef's Table, the UI 4100 may be presented on the FOH device to suggestthat the operator of the FOH device suggest to add the items to theorder.

FIG. 42 , meanwhile, illustrates another example UI 4200 for presentingsuggestions to the operator of the FOH device. As illustrated, the UI4200 includes, at 4202, an indication of the table and, at 4204, onemore suggested items and actions. In this example, the UI 4200 suggeststhat operator suggest, to customers at the Chef's Table, that theyrepeat their last round of drinks. The suggested actions may furtherinclude a suggestion to add an employee discount (perhaps because thecurrent customer is an employee of the establishment 102), a suggestionto split the bill seats, and the like.

FIG. 29 illustrates a flow diagram of another example process 2900. Inthis instance, the process 2900 may determine the identity of anoperator of an FOH device, determine whether the identity is associatedwith prior behavior and, if so, presenting a UI that includes a sequenceof actions that have been customized to the operator based on the priorbehavior.

An operation 2902 represents determining an identifier of a usercurrently operating the FOH device. For instance, this operation maycomprise determining an identifier that is associated with a user thatis currently signed into the FOH device. An operation 2904 representsdetermining whether prior behavior is associated with the determinedidentifier. For example, the analytics data 224 may store patterns ofbehavior associated with different operators of the devices in theestablishments. These patterns of behavior may indicate certainsequences of actions that certain users tend to repeat when operatingthe FOH or other merchant devices. For instance, the analytics data 224may determine that an operator associated with a first identifier oftenchecks her tips before running her shift report, while another operatorassociated with a second identifier often skips this step.

If the identifier is determined to be associated with prior behavior,then an operation 2906 represents generating a sixth UI indicatingcustomized actions to perform based on the prior behavior of the usercurrently operating the FOH device. An operation 2908 represents sendingthe sixth UI for display on the FOH device. For example, the sixth UImay present a sequence of actions that conforms to sequences of actionspreviously performed by the particular operator. Continuing the examplefrom above, for instance, the sixth UI for the first user may begin witha screen for checking her tips, while the sixth UI for the second usermight not include this screen at all.

FIG. 43 , for example, illustrates an example UI 4300 that the FOHdevice may present based on prior behavior of a first operator of theFOH device. At 4302, the UI indicates suggested actions to take, such asprint a latest check for Table 5 (T5), split a check by seat, and thelike. FIG. 44 , however, illustrates an example 4400 that the FOH devicemay present based on prior behavior of a second operator of the FOHdevice. At 4402, the UI 4400 suggests that the operator review tipadjustments, review shift details, and run a shift report. In someinstances, the UIs may include suggested sequences of actions based oninformation that is additional to the prior behavior of the operator,such as a current time and a time at which the operator is expected tolog out of the FOH device (e.g., because their shift is ending).

FIG. 44 further illustrates that an operator of the FOH device mayprovide a selection 4404 for navigating the sequence of actions thathave been customized for the operator based on the prior behavior of theoperator. In response to the selection 4404, FIG. 45 may present a UI4500 that begins by enabling the operator to review her tip adjustmentsat 4502. Again, this screen may be presented on the operator oftenviewing this screen at the end of her shift. The UI 4500 also includesan icon 4504 that is selectable to move from the tip-adjustment screento a shift-details screen. As illustrated, the UI 4500 receives aselection 4506 of this icon 4504.

FIG. 46 presents a UI 4600 that may be presented in response to theselection 4506 of the icon 4504. As illustrated, the UI may include, at4602, details regarding the shift of the operator of the FOH device.These shift details may include an amount of time worked, a time untilthe shift is done, the number of breaks taken by the operator, totalsales, the number of open orders, the number of tips received, and thelike. In addition, the UI 4600 may include an icon 4604 that isselectable to move from the shift-details screen and to running a shiftreport for the operator. The operator provides a selection 4606 in thisexample.

FIG. 47 illustrates an example UI 4700 that the FOH device may presentin response to the selection 4606 of the icon 4604 from the UI 4600. Asillustrated at 4702, this UI 4700 indicates that the FOH device isrunning a shift report for the operator and, potentially, logging theoperator out of the device. FIG. 48 illustrates an example UI 4800 thatthe FOH device may present after running the shift report and loggingout the previous operator.

While FIGS. 44-47 illustrate and describe a customized sequence ofoperations that may be presented based on prior behavior of an operatorof the FOH device, in some instances an operator might not be associatedwith such prior behavior and, thus, might not receive a customizedsequence of actions. Returning to FIG. 29 , if prior behavior is notassociated with the determined identifier (or if a threshold amount ofprior behavior is not associated with the identifier), then an operation2910 may generate a seventh, default UI indicating the actions to take,while an operation 2912 may send the seventh UI for presentation on thedisplay of the FOH device. This default UI may present actions that arenot customized to the current operator of the FOH device, but rathercorresponding a default, non-customized sequence of actions.

FIG. 30 illustrates a flow diagram of another example process 3000 fordetermining if an FOH device is physically coupled to, or within athreshold proximity of, another device and, if so, presenting a UIindicating a sequence of actions to perform. An operation 3002represents determining whether the FOH device is physically coupled toanother device or is within a threshold proximity of another device.This may include determining whether the FOH device is in a cradle,determining (e.g., via Bluetooth) whether an FOH device is near anotherFOH or BOH device, or the like. If so, then an operation 3004 representspresenting, on the display of the FOH device, an eight UI for performingone or more predefined actions. For example, this operation may includepresenting a UI for running a shift report if the FOH device is pluggedinto a cradle or is within a particular device within the establishment102.

FIG. 49 , for example, illustrates an example UI 4900 that an FOH devicemay present prior to being coupled to or within a threshold proximity ofanother device. That is, this UI 4900 may indicate that an operator ofthe FOH device has navigated to a screen to view, at 4902, shift detailsbut not has not yet selected an icon 4904 for running the shift report.

FIG. 50 , however, illustrates an example UI 5000 that the FOH device ofFIG. 49 may present after being physically coupled to another device,such as a receiver 5002. As illustrated, the receiver 5002 may connect,via a wired and/or wireless connection, to one or more other FOH/BOHdevices 200, the remote service 112, and/or the like. Further, thehardware to hardware connections may enable specific software workflowactions. For example, the FOH device may begin running a shift reportautomatically in response to being physical coupled to the receiver5002. In some embodiments, the receiver and the FOH device may be apower supply and power receiving device respectively, however in otherembodiments, the receiver and the FOH device may not provide any powerto the other but instead trigger other actions, such as shift reportgeneration, clock out the server, transfer the tips, etc. The receiver5002 when communicatively coupled with the FOH device can initiatecertain actions pre-configured through rules, e.g., by the merchant orthe remote service. For example, the merchant through BOH can configurethe receiver to finalize shift reports or clock out the FOH server whenthe FOH device is docked in the receiver 5002. The custom rules can alsoenable financial flow from the merchant's financial account to the FOHserver's account, in response to detection of docking of the FOH devicein the receiver 5002. The receiver 5002 can enable the computing deviceto communicate with other devices communicatively coupled to thereceiver (e.g. synchronization with the remote service) and othermerchants, to refine the data displayed on the FOH device. In someimplementations, the control may automatically move from the FOH devicedocked in the receiver 5002 to another device, e.g., another FOH deviceor another customer device, to move the displayed content to that otherdevice. Alternatively, this allows another server to pick up from wherethe previous server left.

FIG. 51 continues the illustration of FIG. 50 and shows, via a UI 5100,that tips are being transferred to an account associated with anoperator of the FOH device. FIG. 52 concludes the illustration of theFIG. 50 and shows, via a UI 5200, that the operator has been logged outof the FOH device. In some instances, the tips may be seamlessly andautomatically transferred to a checking account of the operator, amobile payment application of the operator, and/or the like. Thus, thesequence of UIs 50-52 illustrate that an FOH device may perform apredefined sequence of actions in response to be physically coupled toanother device, such as the cradle 5002.

FIGS. 53 and 54 , meanwhile, illustrate that a predefined sequence ofactions may occur in response to an FOH device within a thresholdproximity of another device in the establishment 102. FIG. 53 , forexample, illustrates an example UI 5300 in which the illustrated FOHdevice detects, and thus is within a threshold proximity of, a“Tableside Device”, which may comprise a device that couples to or isotherwise associated with a particular table or other seating area inthe establishment. The UI 5300 includes an indication 5302 that thedevice has detected the tableside device, and also includes an icon 5304that is selectable to open a new order in response to detecting thetableside device. The UI 5300 illustrates that an operator of the deviceprovides a selection 5306 of the icon 5304. In some implementations,creating an order on a tableside device can tag the order as such, andalso send an alert to the BOH device regarding order and thus enablereal-time communication regarding the orders.

FIG. 54 illustrates an example UI 5400 that the FOH device may presentin response to the selection 5306. As illustrated, the UI 5400illustrates that a new order has been opened, items have been added tothe new order, and so forth. Of course, while a few example sequence ofUIs have been described in response to a merchant device beingphysically coupled to another device or within a threshold proximity ofanother device, other UI sequences may be utilized.

Example Gestures

FIG. 55 and subsequent UIs illustrate different gestures that may causethe establishment application 210 to perform different actions. It is tobe appreciated that while these figures describe example gestures andcorresponding actions, additional gestures may be associated withadditional actions on the establishment application 210 in otherinstances. In some instances, a server, individual devices, and/or thelike may store rules associating the respective gestures with therespective actions. In some instances, these rules may be userconfigurable such that different devices and/or different operatorprofiles may be associated with different rules.

FIGS. 55-62 illustrate, for example, that an operator of the FOH devicemay add or remove different items (e.g., lettuce, tomato, cheese, etc.)from the example item (here, a burger) based on selecting respectivemodifier icons and swiping these icons in a particular direction. Forexample, selecting an icon and swiping to the right may cause theestablishment application 210 to add the modifier to the item, whileselecting an icon and swiping to the left may cause the establishmentapplication 210 to remove the modifier to the item. Further, selectingan icon and swiping upwards may cause the establishment application 210to add an extra amount of the modifier to the item, while selecting anicon and swiping downwards may cause the establishment application 210to indicate that the modifier is to be placed “on the side”. Of course,while example directions are associated with example actions in theseexamples, it is to be appreciated that these are merely illustrative andother directions may be associated with other actions.

In one implementation, the surface of the device accepting gestures,such as sensor pad may include various sensor points, identified in (x,y) coordinates and the sensor pad can identify a user activating one orseveral of these sensor points that ultimately produces sensor data, andin case of several sensor points, the sensor data also records thesequence of the sensor points enabled. The sensor points can be touch ortouchless. When registering the actions, the user can register certainsensor point activation to trigger a certain action. For example, hoveron an item could mean “seeking more information about the item” whereastapping could mean “add to order.” The methods and systems herein allowthe user to define what each gesture can mean in the context of thisorder or in general, their experience with the application. Accordingly,when the user uses the application, the embedded rules are called out inresponse to each gesture to determine the underlying and customizedaction associated with the gesture. The server can also embed optionswith respect to each action to provide sub-actions, as shown in FIG. 64.

FIG. 55 , for example, illustrates a UI 5500 that display examplemodifies at 5502. The UI 5500 also illustrates that an operator of theFOH device provides a selection 5504 corresponding to an icon associatedwith an example modifier (here, lettuce). FIG. 56 illustrates an exampleUI 5600 after the operator makes the selection 5504. Here, operatorbegins to drag the icon towards the right side of the display. FIG. 57 ,meanwhile, illustrates an UI 5700 that shows the operator has continueddragging the icon further to right and, in response, the UI 5700indicates, at 5702, that lettuce has been added to the order. FIG. 58 ,meanwhile, illustrates a UI 5800 in which the user drags the icon backto the left. In response, the UI 5800 indicates, at 5802, that themodifier is to be removed (“No Lettuce”).

FIG. 59 illustrates an example UI 5900 in which the operator of the FOHdevice provides a selection 5902 of another modifier (in this case,“Onions”). FIG. 60 illustrates, via example UI 6000, that the operatormay drag the icon corresponding to the modifier significantly upwards(e.g., greater than a threshold distance from the initial location ofthe icon and/or with a speed that is greater than a threshold speed). Inresponse, the UI 6000 indicates that the name of the icon has changedfrom “Onions” to “Extra Onions”. FIG. 61 illustrates, via a UI 6100 andat 6102, that the item is now associated with “Extra Onions.” Inaddition, however, the UI 6100 illustrates that the operator has changedfrom swiping the icon upwards to downwards, below the initial locationof the icon on the display. In response, the UI 6100 updates the name ofthe modifier from “Extra Onions” to “Side Onions”, given that adownwards swipe is associated with adding the modifier to the side inthis example. FIG. 62 illustrates an example UI 6200 that indicates, at6202, that the modifier has changed from “Extra Onions” to “SideOnions”.

FIGS. 63-67 illustrates additional example UIs and correspondinggestures for adding or removing modifiers from an item, such as theexample burger. FIG. 63 , for instance, illustrates an example UI 6300that lists some of the same example modifiers described above withreference to FIG. 55-62 . Here, the operator provides a selection 6302corresponding to the modifier “Bacon.” FIG. 64 illustrates that the FOHdevice may present a UI 6400 in response. As illustrated, the UI 6400includes an icon 6402 corresponding to the selected modifier, surroundby a menu of options 6404 for the modifier. For example, the modifier(“Bacon”) is surrounded by examples of “Allergy”, “No”, “Sub”, “Extra”,“Add”, and “Side” in this example. Of course, while a few exampleoptions are listed, it is to be appreciated that other implementationsmay utilize additional and/or different options.

FIG. 65 illustrates an example UI 6500 after the operator has selectedthe icon 6402 and begun dragging it towards an option (“Extra”) 6502 ofthe menu of options 6404. As illustrated, the size and/or color of theoption 6404 may change as the icon 6402 nears the option 6502. Forinstance, the size of the option 6502 may enlarge as the icon 6402 nearsthe option 6502. FIG. 66 illustrates an example UI 6600 after theoperator releases the icon 6402 while it is over the option 6502. Asillustrated, the text of the option 6502 has changed to add anindication of the modifier. For example, here, the option 6502 haschanged from “Extra” to “Extra Bacon”. Further, FIG. 67 illustrates anexample UI 6700 that the FOH device may present a predefined amount oftime after the UI 6600 is presented. As illustrated, the menu 6404 ofoptions has disappeared. In addition, the previously selected modifierhas now been changed from its initial text (“Bacon”) to indicate theselected option (“Extra Bacon”).

FIGS. 68-73 illustrates yet another example of gestures for adding orremoving modifiers to an item, such as the example burger. FIG. 68 , forinstance, illustrates an example UI 6800 that illustrates the array ofmodifiers described above. In addition, this UI 6800 indicates that anoperator of the device has provided a selection 6802 corresponding toone of the modifiers (here, “Lettuce”). FIG. 69 presents a UI 6900 inresponse to the selection 6802. As illustrated, the UI 6900 presents amenu of options 6902 alongside the icon corresponding to the selectedmodifier. Again, these example options may include “Extra”, “Add”,“Side”, “Sub”, “No”, and/or the like. In addition, the UI 6900illustrates that the particular option adjacent to the selected modifiericon may change based on a direction of a user input 6904. For example,FIG. 69 illustrates that the operator may swipe upwards after selectingthe icon corresponding to “Lettuce”.

In response to the operator swiping upwards at 6904, FIG. 70illustrates, via example UI 7000, that the option from menu of options6902 has also moved downwards based on the upwards swiping gesture.Thus, while “Add” was previously adjacent to “Lettuce” in FIG. 69 priorto the upwards swiping gesture, “Extra” now appears next to “Lettuce”after the upwards swipe. FIG. 71 , meanwhile, illustrates a UI 7100after the operator has provided a downwards swipe. As illustrated, themenu 6902 has now moved upwards based on the downwards swipe, such thatthe option “No” is now adjacent to the selected modifier icon “Lettuce”.FIG. 72 , meanwhile, illustrate an example UI 7200 after the operatorhas removed the touch input from the touchscreen of the FOH device whilethe option “No” was adjacent to “Lettuce”. In response, the UI 7200 haschanged the modifier to include the option (from “Lettuce” to “NoLettuce”) at 7202. In addition, while this example describes visuallyproviding feedback to the user (e.g., by changing the icon from“Lettuce” to “No Lettuce”), the techniques may additionally oralternatively provide other types of feedback, such as audible feedback,haptic feedback, and/or the like.

FIG. 72 further illustrates that the operator has provided a selection7204 of another modifier (“Fried Onions”). FIG. 73 illustrates anexample UI 7300 that the FOH device may present in response. Asillustrated, the UI 7300 again includes a menu of options 7302, althoughin this instance the menu 7302 appears on the left side of the selectedmodifier. Again, the operator may swipe upwards or downwards to move themenu to the desired location for selecting the desired option. Further,while the examples of FIGS. 68-73 illustrate the menu of options movingopposite the trajectory of the swiping gesture of the operator, in someinstances the menu may move correspondingly to (i.e., in the samedirection as) the swiping gesture.

While the above examples describe a few examples for modifying an item,such as swiping up or down, swiping with a threshold speed, or the like,other examples may enable modification of an item based on one or moreadditional or alternative gestures. For example, the device includes atouch sensor configured to determine an amount of force being applied tothe display and may associate a particular modifier with the item basedon the level of force. For example, if a user lightly touches an icon“lettuce”, this may result in the icon displaying “no lettuce”, whereasif they press harder, the icon may change to “extra lettuce”, or thelike. Further, the devices may be configured to modify an item based onany combination of inputs, such as force, speed, audible commands,and/or the like. Further, the device may be configured to outputnumerous types of output signals to indicate the addition of themodifier, such as an audible tone, a haptic response, a visual response,or the like.

Automatic Generation of Seating-Area Layouts

FIG. 74 illustrates the example architecture 100 of FIG. 1 . Here, amerchant, such as example user 104(2), operates a merchant device, suchas example FOH device 106(2), to capture image data of the establishment102. For example, the FOH device 106(2) may utilize one or more LiDARsensors 200 (e.g. a camera, lighting source, etc.) to generate sensordata of the environment. For example, the LiDAR sensors 200 of thedevice may comprise a light source that illuminates some or a portion ofthe environment and a camera that generates data indicative of an amountand timing of the reflection of the light emitted by the light source.The merchant device may then analyze this sensor data or send thissensor data to the remote service 112 or another device for analysis.The analysis may be effective to identify one or more surfaces (e.g.,flat surfaces) in the establishment 102 that meet certain criteria. Inaddition, the merchant device may present a UI 7400 to enable themerchant to indication which identified surfaces correspond to seatingareas and which do not. After receiving the respective indications fromthe merchant, the merchant device, the remote service 112, or anotherdevice may generate and present on the merchant device a layout ofavailable seating areas in the establishment. Of course, while thisexample describes automatically generating a seating layout of anestablishment, it is to be appreciated that the techniques may apply toautomatically generating any other kind of establishment layout. Forexample, the techniques may be used for generating a layout of aclothing store (e.g., indicating locations where clothes are displayed),a grocery store (indicating locations where food items are located), aclassroom (identifying locations where students sit), and/or any othertype of establishment layout.

Furthermore, it is to be appreciated that the generated layout(s) may beused in conjunction with the techniques described above with referenceto FIGS. 1-73 . For example, after generating a layout of anestablishment, this layout may be used to determine which FOH devicesare associated with (e.g., responsible for) which seating areas withinthe establishment. This information, in turn, may be used to determinewhich FOH and/or BOH devices to establish communication session(s) within order to clarify an order or the like, as described above. Statedotherwise, the techniques described below with reference to FIGS. 74-80may be used with the techniques described above with reference to FIGS.1-73 , such as to help inform devices in the establishment regardingwhich communication sessions to establish with which devices.

In some instances, the remote service 112 may be configured to analyzethe image data of the establishment 102 and generate the layout ofavailable seating areas. Thus, the user 104(2) may operate theestablishment application 210 on the FOH device 106(2) (or othermerchant device) to generate image data of the inside of theestablishment 102 and send this image data to the remote service overthe network 114.

As illustrated, the remote service may comprise one or more processors7402 and computer-readable media 7404 that stores an instance of anestablishment application 7406. In this example, the establishmentapplication 7406 may comprise a data-analysis component 7408, a UIcomponent 7410, a layout component 7412, and a suggestion component7414, along with sensor data 7416 received from merchant devices and oneor more models 7418 for identifying relevant surfaces and determiningsuggested layouts, as described below. Here, flat surfaces areidentified as relevant surfaces, however, depending on the establishment(identified for example via inventory of items offered), the surfacescan be defined in other ways, such as retail surfaces (where in a retailestablishment clothes are hanged), or ecommerce surfaces (wherein agrocery store, shelves are arranged) and so on.

The data-analysis component 7408 may function to receive image or othersensor data received from the FOH device 106(2) and analyze the data toidentify candidate flat surfaces in the environment. In some instances,the data-analysis component 7408 uses computer-vision (CV) techniquesand trained machine-learning models to identify the flat surface. Inother instances, the data-analysis component 7408 uses LiDAR techniquesto identify these surfaces.

In one implementation, the LiDAR sensor performs a scan to collectscanner data that comprises a plurality of scan points. Each scan pointspecifies the range to a surface that was imaged by the LiDAR sensorwhen emitting a laser pulse in a particular direction. The sensor datais then mapped to known surface data to determine the sensor data thatcorresponds to known surface data within threshold error. In oneimplementation, the ML models, such as unsupervised training models orsupervised training models, can be used to identify surfaces, such asdining surfaces, retail surfaces, where the server or the merchant canprovide definitions of such surfaces. The dining surface can be anysurface that is substantially flat and has a specific dimension to allowthe dishes to be laid out. The dining surface for another section of theestablishment may have dimensions enough to accommodate only certainitems, such as drinks. The sensor data can also be used to identifyfurniture, or other stationary objects, within the environment. In someimplementations, a layout API can provide architectural sketches of theenvironment, or comparable environment from similar merchants, thatfeeds into the data-analysis component 7408. The layout API can alsoinclude data such as restaurant menu, inventory, most requested items,etc., to use as training data in the ML models.

In one example, the data-analysis component 7408 may analyze thereceived image data to identify surfaces that meet certain criteria. Insome instances, the criteria may comprise surfaces that aresubstantially parallel to a horizontal plane, surfaces having a surfacearea that is greater than a threshold surface area, surfaces having awidth and/or length that are greater than a respective threshold widthand/or length, surfaces that are elevated a certain distance from afloor (e.g., greater than two feet), surfaces that are within a certainrange of the floor (e.g., two feet to six feet), and/or the like. Thesecriteria help ensure that the identified candidate flat surfacescorrespond to potential seating areas, as opposed to non-seating areaflat surfaces, such as the tops or sides of cabinets, or the like. Inaddition, or in the alternative, the data-analysis component 7408 mayanalyze the received image data to determine a level of glare orreflection, which in turn may be used to determine whether an otherwiseflat surface corresponds to a seating location. For example, given thattables may have some glare while carpet may not, this data may be usedby the trained model(s) for disambiguating an available seating areafrom other flat surfaces, such as the floor.

After the data-analysis component 7408 identifies the candidate flatsurface, the UI component 7410 may generate a UI for presentation on themerchant device to enable the merchant to select which candidate flatsurfaces corresponding to available seating areas and/or which do not.FIG. 78 , for instance, illustrates an example UI 7800 that that UIcomponent 7410 may generate and send to the merchant device. Asillustrated, the UI 7800 may comprise the image data 7802 captured bythe camera of the merchant device, overlaid with respective indications7804(1), 7804(2), and 7804(3) of flat surfaces within the environmentthat the data-analysis component 7408 has identified as meeting thespecified criteria. In some instances, the layout generated as a resultof the image 7802 can also indicate depth, height and other measurementsto create a layout of the entire establishment with demarcated surfaces.

In one example, augmented reality (AR), virtual reality, mixed reality,or a combination thereof can be used to record the “scene” and insertvirtual objects in the real environment. In one implementation, thevirtual objects can be overlaid on a live camera feed with flat surfacesidentified via the LiDAR sensors. In another implementation, the LiDARmodeled environment can act as the virtual canvas on which virtualobjects are overlaid without interacting with the live camera feed.Additionally, or alternatively, relevant aspects of the real environmentof the establishment can be embedded into a virtual layout (e.g., arestaurant canvas, a retail store canvas, a brick or mortar grocerystore canvas, etc.) or restyling a virtual world to better matchreal-time conditions. Elements of a real-time environment can beincorporated in the scene generated by the augmented layout. Elementscan be weather conditions, time parameters, mandatory elements of theestablishment (POS devices, furniture, tableside devices, servers, etc.)can be utilized to augment the layout. In another example, movingelements (e.g., servers taking orders, clothing racks, etc.) can bedetected using the data-analysis component 7408 and incorporated intothe scene. This can involve overlaying the content on real-world imagery(for example, in near real-time) via the computing device, such that theuser of the computing device sees a combination of the real-worldimagery with the AR content seamlessly. In addition, the UI 7800includes a request 7806 to “select which flat surfaces are availableseating areas”. In some instances, the merchant may use the touchscreendisplay or other input mechanism on the merchant device to select whichof the identified candidate flat surfaces 7804(1)-(3) representavailable seating areas in the establishment. For example, the UI 7800may request that the merchant touch those flat surfaces that correspondto available seating areas. In addition, the UI 7800 may enable themerchant to specify the number and/or position of available seats ateach seating area.

FIG. 79 , for instance, illustrates an example UI 7900 after merchanthas selected which of the candidate flat surfaces correspond toavailable seating areas. In this example, the merchant has indicatedthat each of the three flat surfaces 7804(1)-(3) correspond to availableseating areas. After providing these selections and/or indicating thatthe merchant is done, the UI 7900 may present a menu 7902 requesting themerchant to indicate whether they are ready to create a layout orwhether they would like to continue scanning the establishment 102(e.g., walking through the establishment and generating image data ofthe establishment 102).

Returning to FIG. 74 , after the merchant provides input back to theestablishment application 7406 regarding which of the identifiedcandidate flat surfaces correspond to available seating areas in theestablishment 102 and has requested that a layout be generated, thelayout component 7412 may generate a layout of available seating areasin the establishment. FIG. 80 , for instance, illustrates an example UI8000 that the layout component 7412 may generate. As illustrated, the UI8000 indicates, in this example, that the layout of the establishmentincludes an area 8002 of tables and an area 8004 of bar seats. In someinstances, the UI 8000 may provide editing tools to enable the merchantto add, remove, or change parts of the layout. Further, in someinstances, the UI 8000 may include AR objects overlaid onto the layoutto enable the merchant to view what the establishment would look likeunder normal operating conditions. For example, the UI 8000 may enablethe operator of the device to superimpose a layer that includes servers,other employees, appliances, items, and/or any other type of AR objectsthat, when presented on the UI 8000, enables the operator to betterunderstand the generated layout if adopted in the establishment.

Returning again to FIG. 74 , the suggestion component 7414 may functionto generate one or more layout suggestions and present these suggestionsto the merchant. For example, after the layout component 7412 generatesthe layout, the suggestion component 7414 may analyze the generatedlayout to determine whether additional tables can be placed in theestablishment, whether a more efficient layout can be created, or thelike. In some instances, the suggestion component 7412 may use one ormore trained machine-learning models that receive the layout as inputand output one or more alternative layouts that may be suggested to themerchant.

FIG. 75 illustrates a flow diagram of an example process 7500 forgenerating a layout of available seating areas in an establishment. Insome instances, the process 7500, as well as the processes describedbelow, may be performed in whole or in part by a merchant device, theremote service 112, and/or a combination thereof. An operation 7502represents generating image data of a physical establishment of amerchant using a camera of a merchant device. An operation 7504represents determining whether any flat surfaces and correspondinglocations have been identified based on analysis of the image data. Ifnot, then an operation 7506 represents presenting an indication (e.g.,on the merchant device) that no flat surface has been identified.

If one or more flat surfaces and their respective locations in theestablishment are identified, however, then an operation 7508 representspresenting, on a display of the merchant device, the image data overlaidwith respective indications of identified flat surfaces. For example,this operation may include presenting the UI 7800 on the merchantdevice. An operation 7510 represents receiving a selection of first flatsurface, the selection indicating that the first flat surface representsan available seating area in the physical establishment. Again, thisselection may be received via the UI 7800 or in any other manner. Anoperation 7512, meanwhile, represents receiving an indication of anumber of available seats associated with the available seating locationat the first location associated with first flat surface. In someinstances, the merchant uses the merchant device to provide thisindication of the number of available seats.

An operation 7514 represents receiving a selection of the second flatsurface, the selection of the second flat surface indicating that thesecond flat surface is not an available seating area. For example, themerchant may use the UI 7800 to provide the selection indicating thatthe second flat surface is not an available seating area. An operation7516 represents generating, based least in part on the first and secondselections, a layout of available seating areas in the physicalestablishment, the layout of seating areas indicating that the firstflat surface is an available seating at the first location. An operation7518 represents presenting the layout on the display of the merchantdevice. For example, this operation may comprise presenting the UI 8000on the merchant device.

FIG. 76 illustrates a flow diagram of another example process 7400 fordetermining a suggested layout of available seating areas in anestablishment. An operation 7402 represents analyzing the image data todetermine a suggested layout of available seating areas in theestablishment of the merchant. For example, this operation may comprisethe suggestion component 7414 inputting the image data and/or thegenerated layout into a trained machine-learning model. An operation7604 represents determining whether a suggested layout has beendetermined. If not, then the process may end at an operation 7608. If asuggested layout is determined, however, then an operation 7606represents presenting the suggested layout of available seating areas onthe display of the merchant device.

Once the layout has been derived, and AR content objects have beengenerated based on the derived views of the layout, the AR objects couldbe overlaid on top of the layout. Thus, an operation 7610 representsdetermining whether a request has been received (e.g., from a useroperating the device) to add AR objects to the suggested layout, asnoted above. If so, then an operation 7612 represents embedding one ormore AR objects into the suggested layout. If not, then the process mayend at an operation 7614. The operation 7612 may comprise generating theAR objects based on one or more characteristics of the physicalestablishment, such as a type of establishment, objects within theestablishment, and/or the like. For example, if the establishmentcomprises a restaurant, then the generated AR objects may compriseservers, food items, and the like. If the establishment comprises aclothing store, the generated AR objects may comprise clothing itemsand/or the like. The operation 7612 may further comprise associating theAR objects with the image data (e.g., the presented layout) andmodifying the presented layout to include the generated AR objects.Modifying the presented layout may comprise showing the AR objects inthe same view as the presented layout in response to a user request todo so (e.g., a request to present a layer associated with the ARobjects) or, in some instances, modifying the generated layout itselfbased on the AR objects. For instance, the surfaces identified in thelayout may be modified based on the location of the AR objects.

It should be appreciated that the set of AR content objects could beobtained in any suitable manner, including for example, based on asearch query of AR object database (e.g., a search for AR contentobjects that are associated with one or more descriptors that areassociated with one or more views of layout.), based on a characteristicof the initial map (e.g., dimensions, architectural sketch, anindication of the type of establishment, etc.), based on a userselection, recommendation or request (e.g., by an advertiser, merchant,etc.), or based on a context of an intended use of a user (e.g., basedon what activities a user wishes to capture (e.g., shopping, dining,gaming, etc.).

FIG. 77 illustrates a flow diagram of another example process 7700 forgenerating a layout of example seating areas in an establishment. Anoperation 7702 represents receiving data from a device in anenvironment. For example, this operation may comprise receiving imagedata from a merchant device, such as the example FOH device 106(2).

An operation 7704 represents determining whether any flat surfaces andcorresponding locations have been identified. If not, then the process7700 ends at an operation 7706. If so, however, then an operation 7708represents generating a UI indicating the identified flat surfaces andan operation 7710 represents sending the UI to the device, such as themerchant device. In some instances, identifying the flat surfaces andtheir corresponding locations may comprise inputting the data into oneor more trained machine-learning models, using LIDAR techniques toidentify the flat surfaces and their X, Y or X, Y, Z locations in theestablishment, or the like.

An operation 7712 represents receiving, from the device, a selection offirst flat surface indicating that the first flat surface represents anavailable seating area in the environment. For example, this selectionmay be received via the example UI 7900. An operation 7714 representsgenerating, based at least in part on the selection, a layout ofavailable seating areas in the environment, the layout of seating areasindicating that the first flat surface is an available seating at thefirst location, while an operation 7716 represents sending the layout ofthe available seating areas to the device. For example, this operationmay comprise sending the UI 8000 to the merchant device. The generatedlayout may then be used for performing any of the techniques describedabove with reference to operations of the establishment applications 210executing on the BOH and/or FOH devices.

Example Environments and Systems

FIG. 81 illustrates an example environment 8100. The environment 8100includes server computing device(s) 8102 that can communicate over anetwork 81104 with user devices 8106 (which, in some examples can bemerchant devices 8108 (individually, 8108(A)-8108(N))) and/or servercomputing device(s) 8110 associated with third-party serviceprovider(s). The server computing device(s) 8102 can be associated witha service provider 8112 that can provide one or more services for thebenefit of users 8114, as described below. Actions attributed to theservice provider 8112 can be performed by the server computing device(s)8102.

In some instances, the merchant devices 8108 and/or the user devices8106 may correspond to the BOH and/or FOH devices 200 described above.Further, the service computing devices 8102 of the service provider 8112may correspond to server computing devices of the remote service 112, asdescribed in detail above.

With reference to FIG. 81 , the server computing device(s) 8102 cancorrespond to the server computing device(s) of the remote service 112.Furthermore, the user devices 8106 can correspond to the FOH/BOHdevices, or other merchant and/or customer devices. In at least oneexample, the service provider 8112 can correspond to the remote service112 described above.

The environment 8100 can include a plurality of user devices 8106, asdescribed above. Each one of the plurality of user devices 8106 can beany type of computing device such as a tablet computing device, a smartphone or mobile communication device, a laptop, a netbook or otherportable computer or semi-portable computer, a desktop computing device,a terminal computing device or other semi-stationary or stationarycomputing device, a dedicated device, a wearable computing device orother body-mounted computing device, an augmented reality device, avirtual reality device, an Internet of Things (IoT) device, etc. In someexamples, individual ones of the user devices can be operable by users8114. The users 8114 can be referred to as customers, buyers, merchants,sellers, borrowers, employees, employers, payors, payees, couriers, andso on. The users 8114 can interact with the user devices 8106 via userinterfaces presented via the user devices 8106. In at least one example,a user interface can be presented via a web browser, or the like. Inother examples, a user interface can be presented via an application,such as a mobile application or desktop application, which can beprovided by the service provider 8112 or which can be an otherwisededicated application. In at least one example, a user 8114 can interactwith the user interface via touch input, spoken input, or any other typeof input.

As described above, in at least one example, the users 8114 can includemerchants 8116 (individually, 8116(A)-8116(N)). In an example, themerchants 8116 can operate respective merchant devices 8108, which canbe user devices 8106 configured for use by merchants 8116. For thepurpose of this discussion, a “merchant” can be any entity, oremployee/associate of the entity, that offers items (e.g., goods orservices) for purchase or other means of acquisition (e.g., rent,borrow, barter, etc.). The merchants 8116 can offer items for purchaseor other means of acquisition via brick-and-mortar stores, mobile stores(e.g., pop-up shops, food trucks, etc.), online stores, combinations ofthe foregoing, and so forth. In some examples, at least some of themerchants 8116 can be associated with a same entity but can havedifferent merchant locations and/or can have franchise/franchiseerelationships. In additional or alternative examples, the merchants 8116can be different merchants. That is, in at least one example, themerchant 8116(A) is a different merchant than the merchant 8116(B)and/or the merchant 8116(C).

For the purpose of this discussion, “different merchants” can refer totwo or more unrelated merchants. “Different merchants” therefore canrefer to two or more merchants that are different legal entities that donot share accounting, employees, branding, etc. “Different merchants,”as used herein, have different names, employer identification numbers(EIN)s, lines of business (in some examples), inventories (or at leastportions thereof), and/or the like. That is, the use of the term“different merchants” does not refer to a merchant with various merchantlocations or franchise/franchisee relationships.

Each merchant device 8108 can have an instance of a POS application 8118stored thereon. The POS application 8118 can configure the merchantdevice 8108 as a POS terminal, which enables the merchant 8116(A) tointeract with one or more customers 8120. As described above, the users8114 can include customers, such as the customers 8120 shown asinteracting with the merchant 8116(A). For the purpose of thisdiscussion, a “customer” can be any entity that acquires items frommerchants. While only two customers 8120 are illustrated in FIG. 81 ,any number of customers 8120 can interact with the merchants 8116.Further, while FIG. 81 illustrates the customers 8120 interacting withthe merchant 8116(A), the customers 8120 can interact with any of themerchants 8116.

In at least one example, interactions between the customers 8120 and themerchants 8116 that involve the exchange of funds (from the customers8120) for items (from the merchants 8116) can be referred to as “POStransactions” and/or “transactions.” In at least one example, the POSapplication 8118 can determine transaction data associated with the POStransactions. Transaction data can include payment information, whichcan be obtained from a reader device 8122 associated with the merchantdevice 8108(A), user authentication data, purchase amount information,point-of-purchase information (e.g., item(s) purchased, date ofpurchase, time of purchase, etc.), etc. The POS application 8118 cansend transaction data to the server computing device(s) 8102.Furthermore, the POS application 8118 can present a UI to enable themerchant 8116(A) to interact with the POS application 8118 and/or theservice provider 8112 via the POS application 8118.

In at least one example, the merchant device 8108(A) can be aspecial-purpose computing device configured as a POS terminal (via theexecution of the POS application 8118). In at least one example, the POSterminal may be connected to a reader device 8122, which is capable ofaccepting a variety of payment instruments, such as credit cards, debitcards, gift cards, short-range communication-based payment instruments,and the like, as described below. In some examples, the reader device8122 can read information from alternative payment instrumentsincluding, but not limited to, wristbands and the like.

The POS terminal can be paired with a reader device 8122 to comprise aPOS system 8124. The reader device 8122 may physically interact withpayment instruments such as magnetic stripe payment cards, EMV paymentcards, and/or short-range communication (e.g., near field communication(NFC), radio frequency identification (RFID), Bluetooth®, Bluetooth® lowenergy (BLE), etc.) payment instruments. The POS terminal may provide arich user interface, communicate with the reader device 8122, andcommunicate with the server computing device(s) 8102, which can provide,among other services, a payment processing service. The service provider8112 can communicate with server computing device(s) 8110, as describedbelow. In this manner, the POS terminal and reader device 8122 maycollectively process transaction(s) between the merchants 8116 andcustomers 8120. In some examples, POS terminals and reader devices canbe configured in one-to-one pairings. In other examples, the POSterminals and reader devices can be configured in many-to-one pairings(e.g., one POS terminal coupled to multiple reader devices or multiplePOS terminals coupled to one reader device).

While, the POS terminal and the reader device 8122 of the POS system8124 are shown as separate devices, in additional or alternativeexamples, the POS terminal and the reader device 8122 can be part of asingle device. In some examples, the reader device 8122 can have adisplay integrated therein for presenting information to the customers8120. In additional or alternative examples, the POS terminal can have adisplay integrated therein for presenting information to the customers8120. POS systems, such as the POS system 8124, may be mobile, such thatPOS terminals and reader devices may process transactions in disparatelocations across the world. POS systems can be used for processingcard-present transactions and card-not-present (CNP) transactions, asdescribed below.

A card-present transaction is a transaction where both a customer 8120and his or her payment instrument are physically present at the time ofthe transaction. Card-present transactions may be processed by swipes,dips, taps, or any other interaction between a physical paymentinstrument (e.g., a card) and a reader device 8122 whereby the readerdevice 8122 is able to obtain payment data from the payment instrument.A swipe is a card-present transaction where a customer 8120 slides acard, or other payment instrument, having a magnetic strip through areader device 8122 that captures payment data contained in the magneticstrip. A dip is a card-present transaction where a customer 8120 insertsa payment instrument having an embedded microchip (i.e., chip) into areader device 8122 first. The dipped payment instrument remains in thepayment reader until the reader device 8122 prompts the customer 8120 toremove the card, or other payment instrument. While the paymentinstrument is in the reader device 8122, the microchip can create aone-time code which is sent from the POS system 8124 to the servercomputing device(s) 8110 (which can be associated with third-partyservice providers that provide payment services, including but notlimited to, an acquirer bank, an issuer, and/or a card payment network(e.g., Mastercard®, VISA®, etc.)) to be matched with an identicalone-time code. A tap is a card-present transaction where a customer 8120may tap or hover his or her payment instrument (e.g., card, electronicdevice such as a smart phone running a payment application, etc.) over areader device 8122 to complete a transaction via short-rangecommunication (e.g., NFC, RFID, Bluetooth®, BLE, etc.). Short-rangecommunication enables the payment instrument to exchange informationwith the reader device 8122. A tap may also be called a contactlesspayment.

A CNP transaction is a transaction where a card, or other paymentinstrument, are not physically present at the POS such that payment datais required to be manually keyed in (e.g., by a merchant, customer,etc.), or payment data is required to be recalled from a card-on-filedata store, to complete the transaction.

The POS system 8124, the server computing device(s) 8102, and/or theserver computing device(s) 8110 may exchange payment information andtransaction data to determine whether transactions are authorized. Forexample, the POS system 8124 may provide encrypted payment data, userauthentication data, purchase amount information, point-of-purchaseinformation, etc. (collectively, transaction data) to server computingdevice(s) 8102 over the network(s) 81104. The server computing device(s)8102 may send the transaction data to the server computing device(s)8110. As described above, in at least one example, the server computingdevice(s) 8110 can be associated with third-party service providers thatprovide payment services, including but not limited to, an acquirerbank, an issuer, and/or a card payment network (e.g., Mastercard®,VISA®, etc.).

For the purpose of this discussion, the “payment service providers” canbe acquiring banks (“acquirer”), issuing banks (“issuer”), card paymentnetworks, and the like. In an example, an acquirer is a bank orfinancial institution that processes payments (e.g., credit or debitcard payments) and can assume risk on behalf of merchants(s). Anacquirer can be a registered member of a card association (e.g., Visa®,MasterCard®), and can be part of a card payment network. The acquirer(e.g., the server computing device(s) 8110 associated therewith) cansend a fund transfer request to a server computing device of a cardpayment network (e.g., Mastercard®, VISA®, etc.) to determine whetherthe transaction is authorized or deficient. In at least one example, theservice provider 8112 can serve as an acquirer and connect directly withthe card payment network.

The card payment network (e.g., the server computing device(s) 8110associated therewith) can forward the fund transfer request to anissuing bank (e.g., “issuer”). The issuer is a bank or financialinstitution that offers a financial account (e.g., credit or debit cardaccount) to a user. An issuer can issue payment cards to users and canpay acquirers for purchases made by cardholders to which the issuingbank has issued a payment card. The issuer (e.g., the server computingdevice(s) 8110 associated therewith) can make a determination as towhether the customer has the capacity to absorb the relevant chargeassociated with the payment transaction. In at least one example, theservice provider 8112 can serve as an issuer and/or can partner with anissuer. The transaction is either approved or rejected by the issuerand/or the card payment network (e.g., the server computing device(s)8110 associated therewith), and a payment authorization message iscommunicated from the issuer to the POS device via a path opposite ofthat described above, or via an alternate path.

As described above, the server computing device(s) 8110, which can beassociated with payment service provider(s), may determine whether thetransaction is authorized based on the transaction data, as well asinformation relating to parties to the transaction (e.g., the customer8120 and/or the merchant 8116(A)). The server computing device(s) 8110may send an authorization notification over the network(s) 81104 to theserver computing device(s) 8102, which may send the authorizationnotification to the POS system 8124 over the network(s) 81104 toindicate whether the transaction is authorized. The server computingdevice(s) 8102 may also transmit additional information such astransaction identifiers to the POS system 8124. In one example, theserver computing device(s) 8102 may include a merchant applicationand/or other functional modules for communicating with the POS system8124 and/or the server computing device(s) 8110 to authorize or declinetransactions.

Based on the authentication notification that is received by the POSsystem 8124 from server computing device(s) 8110, the merchant 8116(A)may indicate to the customer 8120 whether the transaction has beenapproved. In some examples, approval may be indicated at the POS system8124, for example, at a display of the POS system 8124. In otherexamples, such as with a smart phone or watch operating as a short-rangecommunication payment instrument, information about the approvedtransaction may be provided to the short-range communication paymentinstrument for presentation via a display of the smart phone or watch.In some examples, additional or alternative information can additionallybe presented with the approved transaction notification including, butnot limited to, receipts, special offers, coupons, or loyalty programinformation.

As mentioned above, the service provider 8112 can provide, among otherservices, payment processing services, inventory management services,catalog management services, business banking services, financingservices, web-development services, payroll services, employeemanagement services, appointment services, restaurant managementservices, order management services, delivery/courier services,peer-to-peer payment services, onboarding services, identityverification (IDV) services, and so on. In some examples, the users 8114can access all of the services of the service provider 8112. In otherexamples, the users 8114 can have gradated access to the services, whichcan be based on risk tolerance, IDV outputs, subscriptions, and so on.In at least one example, access to such services can be availed to themerchants 8116 via the POS application 8118. In additional oralternative examples, each service can be associated with its own accesspoint (e.g., application, web browser, etc.).

The service provider 8112 can offer payment processing services forprocessing payments on behalf of the merchants 8116, as described above.For example, the service provider 8112 can provision payment processingsoftware, payment processing hardware and/or payment processing servicesto merchants 8116, as described above, to enable the merchants 8116 toreceive payments from the customers 8120 when conducting POStransactions with the customers 8120. For instance, the service provider8112 can enable the merchants 8116 to receive cash payments, paymentcard payments, and/or electronic payments from customers 8120 for POStransactions and the service provider 8112 can process transactions onbehalf of the merchants 8116.

As the service provider 8112 processes transactions on behalf of themerchants 8116, the service provider 8112 can maintain accounts orbalances for the merchants 8116 in one or more ledgers. For example, theservice provider 8112 can analyze transaction data received for atransaction to determine an amount of funds owed to a merchant 8116(A)for the transaction. In at least one example, such an amount can be atotal purchase price less fees charged by the service provider 8112 forproviding the payment processing services. Based on determining theamount of funds owed to the merchant 8116(A), the service provider 8112can deposit funds into an account of the merchant 8116(A). The accountcan have a stored balance, which can be managed by the service provider8112. The account can be different from a conventional bank account atleast because the stored balance is managed by a ledger of the serviceprovider 8112 and the associated funds are accessible via variouswithdrawal channels including, but not limited to, scheduled deposit,same-day deposit, instant deposit, and a linked payment instrument.

A scheduled deposit can occur when the service provider 8112 transfersfunds associated with a stored balance of the merchant 8116(A) to a bankaccount of the merchant 8116(A) that is held at a bank or otherfinancial institution (e.g., associated with the server computingdevice(s) 8110). Scheduled deposits can occur at a prearranged timeafter a POS transaction is funded, which can be a business day after thePOS transaction occurred, or sooner or later. In some examples, themerchant 8116(A) can access funds prior to a scheduled deposit. Forinstance, the merchant 8116(A) may have access to same-day deposits(e.g., wherein the service provider 8112 deposits funds from the storedbalance to a linked bank account of the merchant on a same day as POStransaction, in some examples prior to the POS transaction being funded)or instant deposits (e.g., wherein the service provider 8112 depositsfunds from the stored balance to a linked bank account of the merchanton demand, such as responsive to a request). Further, in at least oneexample, the merchant 8116(A) can have a payment instrument that islinked to the stored balance that enables the merchant to access thefunds without first transferring the funds from the account managed bythe service provider 8112 to the bank account of the merchant 8116(A).

In at least one example, the service provider 8112 may provide inventorymanagement services. That is, the service provider 8112 may provideinventory tracking and reporting. Inventory management services mayenable the merchant 8116(A) to access and manage a database storing dataassociated with a quantity of each item that the merchant 8116(A) hasavailable (i.e., an inventory). Furthermore, in at least one example,the service provider 8112 can provide catalog management services toenable the merchant 8116(A) to maintain a catalog, which can be adatabase storing data associated with items that the merchant 8116(A)has available for acquisition (i.e., catalog management services). In atleast one example, the catalog may include a plurality of data items anda data item of the plurality of data items may represent an item thatthe merchant 1461(A) has available for acquisition.

In at least one example, the service provider 8112 can provide businessbanking services, which allow the merchant 8116(A) to track deposits(from payment processing and/or other sources of funds) into an accountof the merchant 8116(A), payroll payments from the account (e.g.,payments to employees of the merchant 8116(A)), payments to othermerchants (e.g., business-to-business) directly from the account or froma linked debit card, withdrawals made via scheduled deposit and/orinstant deposit, etc. Furthermore, the business banking services canenable the merchant 8116(A) to check how much money they are earning(e.g., via presentation of available earned balance), understand wheretheir money is going (e.g., via deposit reports (which can include abreakdown of fees), spend reports, etc.), access/use earned money (e.g.,via scheduled deposit, instant deposit, linked payment instrument,etc.), feel in control of their money (e.g., via management of depositschedule, deposit speed, linked instruments, etc.), etc. Moreover, thebusiness banking services can enable the merchants 8116 to visualizetheir cash flow to track their financial health, set aside money forupcoming obligations (e.g., savings), organize money around goals, etc.

In at least one example, the service provider 8112 can provide financingservices and products, such as via business loans, consumer loans, fixedterm loans, flexible term loans, and the like. In at least one example,the service provider 8112 can utilize one or more risk signals todetermine whether to extend financing offers and/or terms associatedwith such financing offers.

In at least one example, the service provider 8112 can provide financingservices for offering and/or lending a loan to a borrower that is to beused for, in some instances, financing the borrower's short-termoperational needs (e.g., a capital loan). For instance, a potentialborrower that is a merchant can obtain a capital loan via a capital loanproduct in order to finance various operational costs (e.g., rent,payroll, inventory, etc.). In at least one example, the service provider8112 can offer different types of capital loan products. For instance,in at least one example, the service provider 8112 can offer a dailyrepayment loan product, wherein a capital loan is repaid daily, forinstance, from a portion of transactions processed by the paymentprocessing service on behalf of the borrower. Additionally and/oralternatively, the service provider 8112 can offer a monthly repaymentloan product, wherein a capital loan is repaid monthly, for instance,via a debit from a bank account linked to the payment processingservice.

Additionally or alternatively, the service provider 8112 can providefinancing services for offering and/or lending a loan to a borrower thatis to be used for, in some instances, financing the borrower's consumerpurchase (e.g., a consumer loan). In at least one example, a borrowercan submit a request for a loan to enable the borrower to purchase anitem from a merchant, which can be one of the merchants 8116. Theservice provider 8112 can generate the loan based at least in part ondetermining that the borrower purchased or intends to purchase the itemfrom the merchant. The loan can be associated with a balance based on anactual purchase price of the item and the borrower can repay the loanovertime. In some examples, the borrower can repay the loan viainstallments, which can be paid via a stored balance associated with theservice provider 8112. The service provider 8112 can offer specificfinancial products, such as payment instruments, tied specifically tothe loan products. For example, in one implementation, the serverprovider 8112 associate capital to a merchant or customer's debit card,where the use of the debit card is defined by the terms of the loan. Insome examples, the merchant may only use the debit card for makingspecific purchases. In other examples, the “installment” associated withthe loan product is credited directly via the payment instrument. Thepayment instrument is thus customized to the loan and/or the partiesassociated with the loan.

The service provider 8112 can provide web-development services, whichenable users 8114 who are unfamiliar with HTML, XML, Javascript, CSS, orother web design tools to create and maintain professional andaesthetically pleasing websites. Some of these web page editingapplications allow users to build a web page and/or modify a web page(e.g., change, add, or remove content associated with a web page).Further, in addition to websites, the web-development services cancreate and maintain other online omni-channel presence, such as socialmedia posts for example.

Furthermore, the service provider 8112 can provide payroll services toenable employers to pay employees for work performed on behalf ofemployers. In at least one example, the service provider 8112 canreceive data that includes time worked by an employee, sales made by theemployee, gratuities received by the employee, and so forth. Based onsuch data, the service provider 8112 can make payroll payments toemployee(s) on behalf of an employer via the payroll service. Forinstance, the service provider 8112 can facilitate the transfer of atotal amount to be paid out for the payroll of an employee from the bankof the employer to the bank of the service provider 8112 to be used tomake payroll payments. In at least one example, when the funds have beenreceived at the bank of the service provider 8112, the service provider8112 can pay the employee, such as by check or direct deposit, often aday, a week, or more after when the work was actually performed by theemployee. In additional or alternative examples, the service provider8112 can enable employee(s) to receive payments via same-day or instantdeposit based at least in part on risk and/or reliability analysesperformed by the service provider 8112.

Moreover, in at least one example, the service provider 8112 can provideemployee management services for managing schedules of employees.Further, the service provider 8112 can provide appointment services forenabling users 8114 to set schedules for scheduling appointments and/orusers 8114 to schedule appointments.

In some examples, the service provider 8112 can provide restaurantmanagement services to enable users 8114 to make and/or managereservations, to monitor front-of-house and/or back-of-house operations,and so on. In at least one example, the service provider 8112 canprovide order management services and/or delivery services to enablerestaurants to manage open tickets, split tickets, and so on and/ormanage delivery services. In some examples, such services can beassociated with restaurant merchants, as described above. In additionalor alternative examples, such services can be any type of merchant.

As described above, the service provider 8112 can provide courierservices, wherein couriers can travel between multiple locations toprovide delivery services, photography services, etc. Couriers can beusers 8114 who can travel between locations to perform services for arequesting user 8114 (e.g., deliver items, capture images, etc.). Insome examples, the courier can receive compensation from the serviceprovider 8112. The courier can employ one or more vehicles, such asautomobiles, bicycles, scooters, motorcycles, buses, airplanes,helicopters, boats, skateboards, etc. Although, in other instances thecourier can travel by foot or otherwise without a vehicle. Some examplesdiscussed herein enable people to participate as couriers in a type ofcrowdsourced service economy. Here, essentially any person with a mobiledevice is able to immediately become a courier, or cease to be acourier, in a courier network that provides services as describedherein. In at least one example, the couriers can be unmanned aerialvehicles (e.g., drones), autonomous vehicles, or any other type ofvehicle capable of receiving instructions for traveling betweenlocations.

In at least one example, the service provider 8112 can provide apeer-to-peer payment service that enables peer-to-peer payments betweentwo or more users 8114. In at least one example, the service provider8112 can communicate with instances of a payment application (or otheraccess point) installed on devices 8106 configured for operation byusers 8114. In an example, an instance of the payment applicationexecuting on a first device operated by a payor can send a request tothe service provider 8112 to transfer an amount of funds (e.g., fiatcurrency or non-fiat currency such as cryptocurrency, securities, andrelated assets) from an account of the payor to an account of a payee(e.g., a peer-to-peer payment). The service provider 8112 can facilitatethe transfer and can send a notification to an instance of the paymentapplication executing on a second mobile device operated by the payeethat the transfer is in process (or has been completed). In someexamples, the service provider 8112 can send additional or alternativeinformation to the instances of the payment application (e.g., lowbalance to the payor, current balance to the payor or the payee, etc.).In some examples, the payor can transfer funds to the payee unprompted.In other examples, the payee can send a request for funds to the payorprior to the payor initiating the transfer of funds. The fundstransferred can be associated with any digital currency type, including,but not limited to, cash, cryptocurrency, etc.

In at least one example, a user 8114 may be new to the service provider8112 such that the user 8114 that has not registered (e.g., subscribedto receive access to one or more services offered by the serviceprovider) with the service provider 8112. The service provider 8112 canoffer onboarding services for registering a potential user 8114 with theservice provider 8112. In some examples, onboarding can involvepresenting various questions, prompts, and the like to a potential user8114 to obtain information that can be used to generate a profile forthe potential user 8114. Responsive to the potential user 8114 providingall necessary information, the potential user 8114 can be onboarded tothe service provider 8112.

The service provider 8112 can be associated with IDV services, which canbe used by the service provider 8112 for compliance purposes and/or canbe offered as a service, for instance to third-party service providers(e.g., associated with the server computing device(s) 8110). That is,the service provider 8112 can offer IDV services to verify the identityof users 8114 seeking to use or using their services. Identityverification requires a customer (or potential customer) to provideinformation that is used by compliance departments to prove that theinformation is associated with an identity of a real person or entity.In at least one example, the service provider 8112 can perform servicesfor determining whether identifying information provided by a user 8114accurately identifies the customer (or potential customer) (i.e., Is thecustomer who they say they are?).

The service provider 8112 is capable of providing additional oralternative services and the services described above are offered as asampling of services. In at least one example, the service provider 8112can exchange data with the server computing device(s) 8110 associatedwith third-party service providers. Such third-party service providerscan provide information that enables the service provider 8112 toprovide services, such as those described above. In additional oralternative examples, such third-party service providers can accessservices of the service provider 8112. That is, in some examples, thethird-party service providers can be subscribers, or otherwise access,services of the service provider 8112.

Techniques described herein can be configured to operate in bothreal-time/online and offline modes. “Online” modes refer to modes whendevices are capable of communicating with the service provider 8112(e.g., the server computing device(s) 8102) and/or the server computingdevice(s) 8110 via the network(s) 81104. In some examples, the merchantdevice(s) 8108 are not capable of connecting with the service provider8112 (e.g., the server computing device(s) 8102) and/or the servercomputing device(s) 8110, due to a network connectivity issue, forexample. In additional or alternative examples, the server computingdevice(s) 8102 are not capable of communicating with the servercomputing device(s) 8110 due to network connectivity issue, for example.In such examples, devices may operate in “offline” mode where at leastsome payment data is stored (e.g., on the merchant device(s) 8108)and/or the server computing device(s) 8102 until connectivity isrestored and the payment data can be transmitted to the server computingdevice(s) 8102 and/or the server computing device(s) 8110 forprocessing.

FIG. 82 depicts an illustrative block diagram illustrating a system 8200for performing techniques described herein. The system 8200 includes auser device 8202, that communicates with server computing device(s)(e.g., server(s) 8204) via network(s) 8206 (e.g., the Internet, cablenetwork(s), cellular network(s), cloud network(s), wireless network(s)(e.g., Wi-Fi) and wired network(s), as well as close-rangecommunications such as Bluetooth®, Bluetooth® low energy (BLE), and thelike). While a single user device 8202 is illustrated, in additional oralternate examples, the system 8200 can have multiple user devices, asdescribed above with reference to FIG. 81 . For example, the user device8202 can correspond to any one of the merchant computing device 104 thephotographer courier computing device 106, or the image capturing device108, as described above with reference to FIG. 1 .

In at least one example, the user device 8202 can be any suitable typeof computing device, e.g., portable, semi-portable, semi-stationary, orstationary. Some examples of the user device 8202 can include, but arenot limited to, a tablet computing device, a smart phone or mobilecommunication device, a laptop, a netbook or other portable computer orsemi-portable computer, a desktop computing device, a terminal computingdevice or other semi-stationary or stationary computing device, adedicated device, a wearable computing device or other body-mountedcomputing device, an augmented reality device, a virtual reality device,an Internet of Things (IoT) device, etc. That is, the user device 8202can be any computing device capable of sending communications andperforming the functions according to the techniques described herein.The user device 8202 can include devices, e.g., payment card readers, ormodules capable of accepting payments, as described below.

In the illustrated example, the user device 8202 includes one or moreprocessors 8208, one or more computer-readable media 8210, one or morecommunication interface(s) 8212, one or more input/output (I/O) devices8214, a display 8216, and sensor(s) 8218.

In at least one example, each processor 8208 can itself comprise one ormore processors or processing cores. For example, the processor(s) 8208can be implemented as one or more microprocessors, microcomputers,microcontrollers, digital signal processors, central processing units,state machines, logic circuitries, and/or any devices that manipulatesignals based on operational instructions. In some examples, theprocessor(s) 8208 can be one or more hardware processors and/or logiccircuits of any suitable type specifically programmed or configured toexecute the algorithms and processes described herein. The processor(s)8208 can be configured to fetch and execute computer-readableprocessor-executable instructions stored in the computer-readable media8210.

Depending on the configuration of the user device 8202, thecomputer-readable media 8210 can be an example of tangiblenon-transitory computer storage media and can include volatile andnonvolatile memory and/or removable and non-removable media implementedin any type of technology for storage of information such ascomputer-readable processor-executable instructions, data structures,program modules or other data. The computer-readable media 8210 caninclude, but is not limited to, RAM, ROM, EEPROM, flash memory,solid-state storage, magnetic disk storage, optical storage, and/orother computer-readable media technology. Further, in some examples, theuser device 8202 can access external storage, such as RAID storagesystems, storage arrays, network attached storage, storage areanetworks, cloud storage, or any other medium that can be used to storeinformation and that can be accessed by the processor(s) 8208 directlyor through another computing device or network. Accordingly, thecomputer-readable media 8210 can be computer storage media able to storeinstructions, modules or modules that can be executed by theprocessor(s) 8208. Further, when mentioned, non-transitorycomputer-readable media exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

The computer-readable media 8210 can be used to store and maintain anynumber of functional modules that are executable by the processor(s)8208. In some implementations, these functional modules compriseinstructions or programs that are executable by the processor(s) 8208and that, when executed, implement operational logic for performing theactions and services attributed above to the user device 8202.Functional modules stored in the computer-readable media 8210 caninclude a user interface 8220 to enable users to interact with the userdevice 8202, and thus the server(s) 8204 and/or other networked devices.In at least one example, the user interface 8220 can be presented via aweb browser, or the like. In other examples, the user interface 8220 canbe presented via an application, such as a mobile application or desktopapplication, which can be provided by a service provider 8112 associatedwith the server(s) 8204, or which can be an otherwise dedicatedapplication. In some examples, the user interface 8220 can be theecommerce user interface 124, the courier user interface 128, or theimage capturing user interface 130. In at least one example, a user caninteract with the user interface via touch input, spoken input, gesture,or any other type of input. The word “input” is also used to describe“contextual” input that may not be directly provided by the user via theuser interface 8220. For example, user's interactions with the userinterface 8220 are analyzed using, e.g., natural language processingtechniques, to determine context or intent of the user, which may betreated in a manner similar to “direct” user input.

Depending on the type of the user device 8202, the computer-readablemedia 8210 can also optionally include other functional modules anddata, such as other modules and data 8222, which can include programs,drivers, etc., and the data used or generated by the functional modules.In some instances, the other modules and data 8222 may comprise the samefunctionality and data as that described above with reference to theMerchant device 114 and other client devices. In addition, thecomputer-readable media 8210 can also store data, data structures andthe like, that are used by the functional modules. Further, the userdevice 8202 can include many other logical, programmatic and physicalmodules, of which those described are merely examples that are relatedto the discussion herein.

In at least one example, the computer-readable media 8210 can includeadditional functional modules, such as an operating system 8224 forcontrolling and managing various functions of the user device 8202 andfor enabling basic user interactions.

The communication interface(s) 8212 can include one or more interfacesand hardware modules for enabling communication with various otherdevices, such as over the network(s) 8206 or directly. For example,communication interface(s) 8212 can enable communication through one ormore network(s) 8206, which can include, but are not limited any type ofnetwork known in the art, such as a local area network or a wide areanetwork, such as the Internet, and can include a wireless network, suchas a cellular network, a cloud network, a local wireless network, suchas Wi-Fi and/or close-range wireless communications, such as Bluetooth®,BLE, NFC, RFID, a wired network, or any other such network, or anycombination thereof. Accordingly, network(s) 8206 can include both wiredand/or wireless communication technologies, including Bluetooth®, BLE,Wi-Fi and cellular communication technologies, as well as wired or fiberoptic technologies. Modules used for such communications can depend atleast in part upon the type of network, the environment selected, orboth. Protocols for communicating over such networks are well known andwill not be discussed herein in detail.

Embodiments of the disclosure may be provided to users through a cloudcomputing infrastructure. Cloud computing refers to the provision ofscalable computing resources as a service over a network, to enableconvenient, on-demand network access to a shared pool of configurablecomputing resources that can be rapidly provisioned and released withminimal management effort or service provider interaction. Thus, cloudcomputing allows a user to access virtual computing resources (e.g.,storage, data, applications, and even complete virtualized computingsystems) in “the cloud,” without regard for the underlying physicalsystems (or locations of those systems) used to provide the computingresources.

The user device 8202 can further include one or more input/output (I/O)devices 8214. The I/O devices 8214 can include speakers, a microphone, acamera, and various user controls (e.g., buttons, a joystick, akeyboard, a keypad, etc.), a haptic output device, and so forth. The I/Odevices 8214 can also include attachments that leverage the accessories(audio-jack, USB-C, Bluetooth, etc.) to connect with the user device8202.

In at least one example, user device 8202 can include a display 8216.Depending on the type of computing device(s) used as the user device8202, the display 8216 can employ any suitable display technology. Forexample, the display 8216 can be a liquid crystal display, a plasmadisplay, a light emitting diode display, an OLED (organic light-emittingdiode) display, an electronic paper display, or any other suitable typeof display able to present digital content thereon. In at least oneexample, the display 8216 can be an augmented reality display, avirtually reality display, or any other display able to present and/orproject digital content. In some examples, the display 8216 can have atouch sensor associated with the display 8216 to provide a touchscreendisplay configured to receive touch inputs for enabling interaction witha graphic interface presented on the display 8216. Accordingly,implementations herein are not limited to any particular displaytechnology. Alternatively, in some examples, the user device 8202 maynot include the display 8216, and information can be presented by othermeans, such as aurally, hapticly, etc.

In addition, the user device 8202 can include sensor(s) 8218. Thesensor(s) 8218 can include a GPS device able to indicate locationinformation. Further, the sensor(s) 8218 can include, but are notlimited to, an accelerometer, gyroscope, compass, proximity sensor,camera, microphone, and/or a switch.

Additionally, the user device 8202 can include various other modulesthat are not shown, examples of which include removable storage, a powersource, such as a battery and power control unit, a barcode scanner, aprinter, a cash drawer, and so forth.

In addition, in some examples, the user device 8202 can include, beconnectable to, or otherwise be coupled to a reader device 8226, forreading payment instruments and/or identifiers associated with paymentobjects. In some examples, as described above, the reader device 8226can plug in to a port in the user device 8202, such as amicrophone/headphone port, a data port, or other suitable port. Inadditional or alternative examples, the reader device 8226 can becoupled to the user device 8202 via another wired or wirelessconnection, such as via a Bluetooth®, BLE, and so on. The reader device8226 can include a read head for reading a magnetic strip of a paymentcard, and further can include encryption technology for encrypting theinformation read from the magnetic strip. Additionally or alternatively,the reader device 8226 can be an EMV payment reader, which in someexamples, can be embedded in the user device 8202. Moreover, numerousother types of readers can be employed with the user device 8202 herein,depending on the type and configuration of the user device 8202.

The reader device 8226 may be a portable magnetic stripe card reader,optical scanner, smartcard (card with an embedded IC chip) reader (e.g.,an EMV-compliant card reader or short-range communication-enabledreader), RFID reader, or the like, configured to detect and obtain dataoff any payment instrument. Accordingly, the reader device 8226 mayinclude hardware implementation, such as slots, magnetic tracks, andrails with one or more sensors or electrical contacts to facilitatedetection and acceptance of a payment instrument. That is, the readerdevice 8226 may include hardware implementations to enable the readerdevice 8226 to interact with a payment instrument via a swipe (i.e., acard-present transaction where a customer slides a card having amagnetic strip through a payment reader that captures payment datacontained in the magnetic strip), a dip (i.e., a card-presenttransaction where a customer inserts a card having an embedded microchip(i.e., chip) into a payment reader first until the payment readerprompts the customer to remove the card), or a tap (i.e., a card-presenttransaction where a customer may tap or hover his or her electronicdevice such as a smart phone running a payment application over apayment reader to complete a transaction via short-range communication)to obtain payment data associated with a customer. Additionally oroptionally, the reader device 8226 may also include a biometric sensorto receive and process biometric characteristics and process them aspayment instruments, given that such biometric characteristics areregistered with the payment service system and connected to a financialaccount with a bank server.

The reader device 8226 may include processing unit(s), computer-readablemedia, a reader chip, a transaction chip, a timer, a clock, a networkinterface, a power supply, and so on. The processing unit(s) of thereader device 8226 may execute one or more modules and/or processes tocause the reader device 8226 to perform a variety of functions, as setforth above and explained in further detail in the following disclosure.In some examples, the processing unit(s) may include a centralprocessing unit (CPU), a graphics processing unit (GPU), a CPU and aGPU, or processing units or modules known in the art. Additionally, eachof the processing unit(s) may possess its own local memory, which alsomay store program modules, program data, and/or one or more operatingsystems. Depending on the exact configuration and type of the readerdevice 8226, the computer-readable media may include volatile memory(such as RAM), non-volatile memory (such as ROM, flash memory, miniaturehard drive, memory card, or the like), or some combination thereof. Inat least one example, the computer-readable media of the reader device8226 may include at least one module for performing various functions asdescribed herein.

The reader chip may perform functionalities to control the operationsand processing of the reader device 8226. That is, the reader chip mayperform functionalities to control payment interfaces (e.g., acontactless interface, a contact interface, etc.), a wirelesscommunication interface, a wired interface, a user interface (e.g., asignal condition device (FPGA)), etc. Additionally, the reader chip mayperform functionality to control the timer, which may provide a timersignal indicating an amount of time that has lapsed following aparticular event (e.g., an interaction, a power-down event, etc.).Moreover, the reader chip may perform functionality to control theclock, which may provide a clock signal indicating a time. Furthermore,the reader chip may perform functionality to control the networkinterface, which may interface with the network(s) 8206, as describedbelow.

Additionally, the reader chip may perform functionality to control thepower supply. The power supply may include one or more power suppliessuch as a physical connection to AC power or a battery. Power supply mayinclude power conversion circuitry for converting AC power andgenerating a plurality of DC voltages for use by modules of readerdevice 8226. When power supply includes a battery, the battery may becharged via a physical power connection, via inductive charging, or viaany other suitable method.

The transaction chip may perform functionalities relating to processingof payment transactions, interfacing with payment instruments,cryptography, and other payment-specific functionality. That is, thetransaction chip may access payment data associated with a paymentinstrument and may provide the payment data to a POS terminal, asdescribed above. The payment data may include, but is not limited to, aname of the customer, an address of the customer, a type (e.g., credit,debit, etc.) of a payment instrument, a number associated with thepayment instrument, a verification value (e.g., PIN Verification KeyIndicator (PVKI), PIN Verification Value (PVV), Card Verification Value(CVV), Card Verification Code (CVC), etc.) associated with the paymentinstrument, an expiration data associated with the payment instrument, aprimary account number (PAN) corresponding to the customer (which may ormay not match the number associated with the payment instrument),restrictions on what types of charges/debts may be made, etc.Additionally, the transaction chip may encrypt the payment data uponreceiving the payment data.

It should be understood that in some examples, the reader chip may haveits own processing unit(s) and computer-readable media and/or thetransaction chip may have its own processing unit(s) andcomputer-readable media. In other examples, the functionalities ofreader chip and transaction chip may be embodied in a single chip or aplurality of chips, each including any suitable combination ofprocessing units and computer-readable media to collectively perform thefunctionalities of reader chip and transaction chip as described herein.

While, the user device 8202, which can be a POS terminal, and the readerdevice 8226 are shown as separate devices, in additional or alternativeexamples, the user device 8202 and the reader device 8226 can be part ofa single device, which may be a battery-operated device. In such anexample, modules of both the user device 8202 and the reader device 8226may be associated with the single device. In some examples, the readerdevice 8226 can have a display integrated therewith, which can be inaddition to (or as an alternative of) the display 8216 associated withthe user device 8202.

The server(s) 8204 can include one or more servers or other types ofcomputing devices that can be embodied in any number of ways. Forexample, in the example of a server, the modules, other functionalmodules, and data can be implemented on a single server, a cluster ofservers, a server farm or data center, a cloud-hosted computing service,a cloud-hosted storage service, and so forth, although other computerarchitectures can additionally or alternatively be used. In at least oneexample, the server(s) 8204 can correspond to the server computingdevice(s) 102 described above with reference to FIG. 1 .

Further, while the figures illustrate the modules and data of theserver(s) 8204 as being present in a single location, these modules anddata can alternatively be distributed across different computing devicesand different locations in any manner. Consequently, the functions canbe implemented by one or more server computing devices, with the variousfunctionality described above distributed in various ways across thedifferent computing devices. Multiple server(s) 8204 can be locatedtogether or separately, and organized, for example, as virtual servers,server banks and/or server farms. The described functionality can beprovided by the servers of a single merchant or enterprise, or can beprovided by the servers and/or services of multiple different customersor enterprises.

In the illustrated example, the server(s) 8204 can include one or moreprocessors 8228, one or more computer-readable media 8230, one or moreI/O devices 8232, and one or more communication interfaces 8234. Eachprocessor 8228 can be a single processing unit or a number of processingunits and can include single or multiple computing units or multipleprocessing cores. The processor(s) 8228 can be implemented as one ormore microprocessors, microcomputers, microcontrollers, digital signalprocessors, central processing units, state machines, logic circuitries,and/or any devices that manipulate signals based on operationalinstructions. For example, the processor(s) 8228 can be one or morehardware processors and/or logic circuits of any suitable typespecifically programmed or configured to execute the algorithms andprocesses described herein. The processor(s) 8228 can be configured tofetch and execute computer-readable instructions stored in thecomputer-readable media 8230, which can program the processor(s) 8228 toperform the functions described herein.

The computer-readable media 8230 can include volatile and nonvolatilememory and/or removable and non-removable media implemented in any typeof technology for storage of information, such as computer-readableinstructions, data structures, program modules, or other data. Suchcomputer-readable media 8230 can include, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, optical storage,solid state storage, magnetic tape, magnetic disk storage, RAID storagesystems, storage arrays, network attached storage, storage areanetworks, cloud storage, or any other medium that can be used to storethe desired information and that can be accessed by a computing device.Depending on the configuration of the server(s) 8204, thecomputer-readable media 8230 can be a type of computer-readable storagemedia and/or can be a tangible non-transitory media to the extent thatwhen mentioned, non-transitory computer-readable media exclude mediasuch as energy, carrier signals, electromagnetic waves, and signals perse.

The computer-readable media 8230 can be used to store any number offunctional modules that are executable by the processor(s) 8228. In manyimplementations, these functional modules comprise instructions orprograms that are executable by the processors 8228 and that, whenexecuted, specifically configure the one or more processors 8228 toperform the actions attributed above to the service provider 8112 and/orpayment processing service. Functional modules stored in thecomputer-readable media 8230 can optionally include a merchant module8236, a training module 8238, and one or more other modules and data8240.

The merchant module 8236 can be configured to receive transaction datafrom POS systems, such as the POS system 8124 described above withreference to FIG. 81 . The merchant module 8236 can transmit requests(e.g., authorization, capture, settlement, etc.) to payment serviceserver computing device(s) to facilitate POS transactions betweenmerchants and customers. The merchant module 8236 can communicate thesuccesses or failures of the POS transactions to the POS systems. Insome examples, the payment processing module 116, described above, andthe merchant module 8236 can perform the same or similar functions.

The training module 8238 can be configured to train models usingmachine-learning mechanisms. For example, a machine-learning mechanismcan analyze training data to train a data model that generates anoutput, which can be a recommendation, a score, and/or anotherindication. Machine-learning mechanisms can include, but are not limitedto supervised learning algorithms (e.g., artificial neural networks,Bayesian statistics, support vector machines, decision trees,classifiers, k-nearest neighbor, etc.), unsupervised learning algorithms(e.g., artificial neural networks, association rule learning,hierarchical clustering, cluster analysis, etc.), semi-supervisedlearning algorithms, deep learning algorithms, etc.), statisticalmodels, etc. In at least one example, machine-trained data models can bestored in a datastore associated with the user device(s) 8202 and/or theserver(s) 8204 for use at a time after the data models have been trained(e.g., at runtime).

The one or more other modules and data 8240 can include programs,drivers, etc., and the data used or generated by the functional modules.Further, the server(s) 8204 can include many other logical, programmaticand physical modules, of which those described above are merely examplesthat are related to the discussion herein. In some instances, the othermodules and data 8222 may comprise the same functionality and data asthat described above with reference to the remote service 112.

The one or more “modules” referenced herein may be implemented as moremodules or as fewer modules, and functions described for the modules maybe redistributed depending on the details of the implementation. Theterm “module,” as used herein, refers broadly to software stored onnon-transitory storage medium (e.g., volatile or non-volatile memory fora computing device), hardware, or firmware (or any combination thereof)modules. Modules are typically functional such that they that maygenerate useful data or other output using specified input(s). A modulemay or may not be self-contained. An application program (also called an“application”) may include one or more modules, or a module may includeone or more application programs that can be accessed over a network ordownloaded as software onto a device (e.g., executable code causing thedevice to perform an action). An application program (also called an“application”) may include one or more modules, or a module may includeone or more application programs. In some examples, a module may includeone or more application programming interfaces (APIs) to perform some orall of its functionality (e.g., operations). In additional and/oralternative examples, the module(s) may be implemented ascomputer-readable instructions, various data structures, and so forthvia at least one processing unit to configure the computing device(s)described herein to execute instructions and to perform operations asdescribed herein.

The computer-readable media 8230 can additionally include an operatingsystem 8242 for controlling and managing various functions of theserver(s) 8204.

The communication interface(s) 8234 can include one or more interfacesand hardware modules for enabling communication with various otherdevices, such as over the network(s) 8206 or directly. For example,communication interface(s) 8234 can enable communication through one ormore network(s) 8206, which can include, but are not limited any type ofnetwork known in the art, such as a local area network or a wide areanetwork, such as the Internet, and can include a wireless network, suchas a cellular network, a local wireless network, such as Wi-Fi and/orclose-range wireless communications, such as Bluetooth®, BLE, NFC, RFID,a wired network, or any other such network, or any combination thereof.Accordingly, network(s) 8206 can include both wired and/or wirelesscommunication technologies, including Bluetooth®, BLE, Wi-Fi andcellular communication technologies, as well as wired or fiber optictechnologies. Modules used for such communications can depend at leastin part upon the type of network, the environment selected, or both.Protocols for communicating over such networks are well known and willnot be discussed herein in detail.

The server(s) 8204 can further be equipped with various I/O devices8232. Such I/O devices 8232 can include a display, various userinterface controls (e.g., buttons, joystick, keyboard, mouse, touchscreen, biometric or sensory input devices, etc.), audio speakers,connection ports and so forth.

In at least one example, the system 8200 can include a datastore 8244that can be configured to store data that is accessible, manageable, andupdatable. In some examples, the datastore 8244 can be integrated withthe user device 8202 and/or the server(s) 8204. In other examples, asshown in FIG. 82 , the datastore 8244 can be located remotely from theserver(s) 8204 and can be accessible to the server(s) 8204. Thedatastore 8244 can comprise multiple databases and/or servers connectedlocally and/or remotely via the network(s) 8206.

In at least one example, the datastore 8244 can store user profiles,which can include merchant profiles, customer profiles, courierprofiles, and so on, as described above. Furthermore, in at least oneexample, the datastore 8244 can store inventory database(s) and/orcatalog database(s). As described above, an inventory can store dataassociated with a quantity of each item that a merchant has available tothe merchant. Furthermore, a catalog can store data associated withitems that a merchant has available for acquisition. The datastore 8244can store additional or alternative types of data (e.g., image(s) 120,etc.) as described herein.

In at least one example, the datastore 8244 can be associated with abrand asset database, which can store information associated with brandassets associated with merchants. A brand asset can be a logo (e.g.,text logo, graphic logo, favicon, etc.), a font, a color, an image, anicon, a button style, effects, spacing, and the like used in associationwith a brand of the merchant. In some examples, a brand asset can beassociated with multiple content items, which can be applicable todifferent end users and/or intended viewers. For instance, a brand assetcorresponding to a logo can be associated with a logo that is presentedto customers and a logo that is presented to merchants. In someexamples, image(s) captured via techniques described herein can be addedto the brand asset database and/or data associated with the brand assetdatabase can be used for informing guidance as described herein.

The phrases “in some examples,” “according to various examples,” “in theexamples shown,” “in one example,” “in other examples,” “variousexamples,” “some examples,” and the like generally mean the particularfeature, structure, or characteristic following the phrase is includedin at least one example of the present invention, and may be included inmore than one example of the present invention. In addition, suchphrases do not necessarily refer to the same examples or to differentexamples.

If the specification states a module or feature “can,” “may,” “could,”or “might” be included or have a characteristic, that particular moduleor feature is not required to be included or have the characteristic.

Further, the aforementioned description is directed to devices andapplications that are related to payment technology. However, it will beunderstood, that the technology can be extended to any device andapplication. Moreover, techniques described herein can be configured tooperate irrespective of the kind of payment object reader, POS terminal,web applications, mobile applications, POS topologies, payment cards,computer networks, and environments.

Various techniques described herein refer to “requests” and/or“prompts.” For the purpose of this discussion, a “request” or a “prompt”can be a data item transmitted between computing devices describedherein with instructions for performing and/or taking an action (e.g., a“request”) and/or a recommendation for performing and/or taking anaction (e.g., a “prompt”). In some examples, the “requests” and/or“prompts” can be associated with graphical user interface (GUI) elementsthat are to be presented via a user interface to communicate theinstructions to a user of a respective user device.

Various figures included herein are flowcharts showing example methodsinvolving techniques as described herein. The methods illustrated aredescribed for convenience and ease of understanding. However, themethods illustrated are not limited to being performed using modulesdescribed in the illustrated figures, and such modules are not limitedto performing the methods illustrated herein.

Furthermore, the methods described above are illustrated as collectionsof blocks in logical flow graphs, which represent sequences ofoperations that can be implemented in hardware, software, or acombination thereof. In the context of software, the blocks representcomputer-executable instructions stored on one or more computer-readablestorage media that, when executed by processor(s), perform the recitedoperations. Generally, computer-executable instructions includeroutines, programs, objects, modules, data structures, and the like thatperform particular functions or implement particular abstract datatypes. The order in which the operations are described is not intendedto be construed as a limitation, and any number of the described blockscan be combined in any order and/or in parallel to implement theprocesses. In some embodiments, one or more blocks of the process can beomitted entirely. Moreover, the methods can be combined in whole or inpart with each other or with other methods.

What is claimed is:
 1. A method comprising: presenting, on a display ofa back-of-house (BOH) device associated with an order preparation areaof a merchant and operated by one or more merchant employees, a firstuser interface (UI) including details associated with a first order thatoriginated from a first front-of-house (FOH) device and detailsassociated with a second order originated from a second FOH device,wherein the first FOH device and the second FOH device are bothassociated with an order taking area of the merchant and are operated byone or more merchant employees while within the order taking area orwhile within the order preparation area; receiving, via the first UI andat the BOH device, a first selection of the first order; presenting, inresponse to the first selection and on the display of the BOH device, asecond UI including details regarding the first order; receiving, viathe second UI and at the BOH device, a second selection comprising arequest corresponding to the first order; determining, by the BOHdevice, to establish a dedicated communication session between the BOHdevice and the first FOH device based at least in part on a distancebetween the first FOH device and a table associated with the firstorder; establishing a dedicated communication session between the BOHdevice and the first FOH device at least partly in response to thedetermining and the receiving of the second selection; and sending, viathe dedicated communication session, from the BOH device, and to thefirst FOH device, an indication of the request.
 2. The method as recitedin claim 1, wherein: the receiving of the request comprises generating aquery regarding the first order; and the sending the indicationcomprises sending an indication of the query to the first FOH device. 3.The method as recited in claim 1, wherein the sending the indication ofthe request further comprises sending an indication of a physicallocation in an establishment at which the BOH device resides.
 4. Themethod as recited in claim 1, further comprising: presenting, on thedisplay of the BOH device, a third UI including details regarding thesecond order; receiving, via the third UI, an indication that an itemwithin the second order has been prepared; determining that the secondFOH device originated the second order that includes the item;establishing a communication session with the second FOH device; andsending, via the communication session with the second FOH device and tothe second FOH device, an indication that the item has been prepared. 5.The method as recited in claim 1, further comprising: presenting, on thedisplay of the BOH device, a third UI including details regarding thesecond order; receiving, via the third UI, an indication that a user hasbegun preparing an item within the second order; determining that thesecond FOH device originated the second order that includes the item;establishing a communication session with the second FOH device; andsending, via the communication session with the second FOH device and tothe second FOH device, an indication that the user has begun preparingthe item.
 6. The method as recited in claim 1, further comprisingpresenting, on the display of the BOH device, a third UI indicating: (i)that a current or predicted number of orders to be prepared using afirst appliance is greater than a capacity associated with the firstappliance, and (ii) a suggestion to activate a second appliance forpreparing at least a portion of the current or predicted number oforders.
 7. The method as recited in claim 6, wherein the third UIfurther includes an icon for activating the second appliance, andfurther comprising: receiving a selection of the icon via the third UI;and causing activation of the second appliance at least partly inresponse to the receiving of the selection of the icon.
 8. The method asrecited in claim 7, further comprising presenting, on the display of theBOH device and in response to the selection of the icon, a fourth UIindicating at least one of a number of orders to be prepared using thefirst appliance and a number of orders to be prepared using the secondappliance.
 9. A method implemented at least in part by a first device,the method comprising: presenting, on a display of the first deviceassociated with an order preparation area of a merchant and operated byone or more merchant employees, a first user interface (UI) includingdetails associated with a first order that originated from a seconddevice and details associated with a second order originated from athird device, wherein the second device and the third device are bothassociated with an order taking area of the merchant and are operated byone or more merchant employees while within the order taking area orwhile within the order preparation area; receiving, via the first UI andat the first device, a first selection of the first order; presenting,in response to the first selection and on the display of the firstdevice, a second UI including details regarding the first order;receiving, via the second UI and at the first device, a second selectioncomprising a request corresponding to the first order; determining, bythe first device, to establish a dedicated communication session betweenthe first device and the second device based at least in part on adistance between the second device and a table associated with the firstorder; establishing a communication session between the first device andthe second device at least partly in response to the determining and thereceiving of the second selection; and sending, via the communicationsession, from the first device, and to the second device, an indicationof the request.
 10. The method as recited in claim 9, wherein: thereceiving of the request comprises generating a query regarding thefirst order; and the sending the indication comprises sending anindication of the query to the second device.
 11. The method as recitedin claim 9, wherein the sending the indication of the request furthercomprises sending an indication of a physical location in anestablishment at which the first device resides.
 12. The method asrecited in claim 9, further comprising: presenting, on the display ofthe first device, a third UI including details regarding the secondorder; receiving, via the third UI, an indication that an item withinthe second order has been prepared; determining that the third deviceoriginated the second order that includes the item; establishing acommunication session with the third device; and sending, via thecommunication session with the third device and to the third device, anindication that the item has been prepared.
 13. The method as recited inclaim 9, further comprising: presenting, on the display of the firstdevice, a third UI including details regarding the second order;receiving, via the third UI, an indication that a user has begunpreparing an item within the second order; determining that the thirddevice originated the second order that includes the item; establishinga communication session with the third device; and sending, via thecommunication session with the third device and to the third device, anindication that the user has begun preparing the item.
 14. The method asrecited in claim 9, further comprising presenting, on the display of thefirst device, a third UI indicating: (i) that a current or predictednumber of orders to be prepared using a first appliance is greater thana capacity associated with the first appliance, and (ii) a suggestion toactivate a second appliance for preparing at least a portion of thecurrent or predicted number of orders.
 15. The method as recited inclaim 14, wherein the third UI further includes an icon for activatingthe second appliance, and further comprising: receiving a selection ofthe icon via the third UI; and causing activation of the secondappliance at least partly in response to the receiving of the selectionof the icon.
 16. The method as recited in claim 15, further comprisingpresenting, on the display of the first device and in response to theselection of the icon, a fourth UI indicating at least one of a numberof orders to be prepared using the first appliance and a number oforders to be prepared using the second appliance.
 17. A first devicecomprising: a display; one or more processors; and one or morecomputer-readable media storing computer-executable instructions that,when executed, cause the one or more processors to perform actscomprising: presenting, on the display of the first device associatedwith an order preparation area of a merchant and operated by one or moremerchant employees, a first user interface (UI) including detailsassociated with a first order that originated from a second device anddetails associated with a second order originated from a third device,wherein the second device and the third device are both associated withan order taking area of the merchant and are operated by one or moremerchant employees while within the order taking area or while withinthe order preparation area; receiving, via the first UI, a firstselection of the first order; presenting, in response to the firstselection and on the display of the first device, a second UI includingdetails regarding the first order; receiving, via the second UI, asecond selection comprising a request corresponding to the first order;determining, by the first device, to establish a dedicated communicationsession between the first device and the second device based at least inpart on a distance between the second device and a table associated withthe first order; establishing a communication session between the firstdevice and the second device at least partly in response to thedetermining and the receiving of the second selection; and sending, viathe communication session and to the second device, an indication of therequest.
 18. The first device as recited in claim 17, wherein: thereceiving of the request comprises generating a query regarding thefirst order; and the sending the indication comprises sending anindication of the query to the second device.
 19. The first device asrecited in claim 17, wherein at least one of: the first device comprisesa back-of-house (BOH) device and the second device comprises afront-of-house (FOH) device; or the first device comprises the FOHdevice and the second device comprises the BOH device.
 20. The firstdevice as recited in claim 17, the acts further comprising: presenting,on the display of the first device, a third UI including detailsregarding the second order; receiving, via the third UI, an indicationthat an item within the second order has been prepared; determining thatthe third device originated the second order that includes the item;establishing a communication session with the third device; and sending,via the communication session with the third device and to the thirddevice, an indication that the item has been prepared.